Introduction
Juniper's Case APIs consist of 10 APIs and two push notifications. The JSON representations for each API request and response are provided below. JSON Key Details provides details of each json key such as data type, data size, description, requirements and comments to help you learn about the APIs. See Examples for the different APIs.
Note The synchronous response to an api request will always be a http response with code of 200 or 400. (Success or Client Error).
The response payload has four key attributes (viz. statusCode, status, message and an optional fault array) for the Client application to pay attention too.
- A response with the payload having statusCode of 200 indicates request has been processed successfully and no further action is required.
- A response with the payload having statusCode of 300 indicates that the request has been processed successfully BUT there are some warning class messages in the fault array that must be reviewed.
- A Client Error response will always have in the payload a fault array with one or more errors.
In publishSR, if statusCode is 300 it indicates that the payload has a fault array in it with one or more Warning class messages.
Required headers in each API request sent
The following are the required headers to be sent in each CaseAPI call.
Headers | Value |
---|---|
Authorization | Required (string) for OIDC based authorization i.e. OIDC ID token Example Bearer WQiOiJzMTBZa0hZNnRhVHgtWFNidWttV2ZkZW5Hb2x1Q2NlVkI3VWU1Z2JoTm5rIiwiYWxnIjoiUlMyNTYifQ.WIiOiIwMHVtYm84OHprZEJRVmxKTjBoNyIsIm5hbWUiOiJWZW5rYXQgQmVsbGFta29uZGEiLCJsb2NhbGUiOiJlbi1VUyIsInZlciI6MSwiaXNzIjoiaHR0cHM6Ly9qdW5pcGVyLXBvYy5va3RhcHJldmlldy5jb20vb2F1dGgyL2RlZmF1bHQiLCJhdWQiOiIwb2FmdHBqYXRrRmc5a3VuazBoNyIsImlhdCI6MTU3NDc4ODY5MSwiZXhwIjoxNTc0NzkyMjkxLCJqdGkiOiJJRC5VbFlibmVRVkxhekVpS0pXS2QwLUlERm96TV9sTGVoYzIwY1JFd2VGRUVBIiwiYW1yIjpbInB3ZCJdLCJpZHAiOiIwMG9mdGUxYXFjY1JrUTZmTTBoNyIsIm5vbmNlIjoicHNtZ1lWeFB6MlRIbUFmSTZlN0F5Q1NQc3o5TWtHaHciLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJ2ZW5rYXRiQGp1bmlwZXIubmV0IiwiZ2l2ZW5fbmFtZSI6IlZlbmthdCIsImZhbWlseV9uYW1lIjoiQmVsbGFta29uZGEiLCJ6b25laW5mbyI6IkFtZXJpY2EvTG9zX0FuZ2VsZXMiLCJ1cGRhdGVkX2F0IjoxNTY0NjE1MzUxLCJhdXRoX3RpbWUiOjE1NzQ3ODg2OTB9.yq_Udq_h4JcEbSJJI9uRJD6PtESsnj9qAzd8R0D4nNechWUAeiCThGJCFGn--MSRM-fhek8IY9RrXltUiRqDBTthTxKQHWt-JIp4zGNBVep0IGVE64SjK8dvD84-M1D3n-ZPWKusvQGtqpJPbeQoSeNrJulA-tdWZLS6Q3ke_0uUiuK7iWHnHX2m_VqKz0sga_uQmYCMTI_FBsqTfFrpSwoZCCXSE4sB-m3lLGy4Ho8PZEmYqlB6fxGnzui08cuNhjgsJKPMyohXJ2hwQQwBYxfSGRXa7g-adPSGoBbvDqYiDS0ijCwzRRxS_k2vr-I5vVTAtNjewozIFV0Um4-Tdg |
Accept | application/json |
Content-Type | application/json |
createSR
Create a Service Request and associate it with the customerCaseNumber from the request.
Note: createSR response will NOT contain the Juniper serviceRequestNumber. The publishSR sent asynchronously to the client endpoint after the creation of the service request includes the serviceRequestNumber along with the customerCaseNumber sent in the request. The customerCaseNumber must be unique in each createSR request.
{
"createSRRequest": {
"appId": "string",
"userId": "string",
"requestDateTime": "string",
"caseInformation": {
"caseTypeCode": "string",
"customerCaseNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string",
"addSenderToEmail": boolean,
"ccEmail": "string",
"followUpMethod": "string",
"networkOutage": boolean,
"synopsis": "string",
"priority": "string",
"adminSRType": "string",
"adminSRSubType": "string",
"problemDescription": "string"
},
"contact": {
"accountID": "string",
"contactEmail": "string",
"preferredTelephoneCountryCode": "string",
"preferredTelephoneNumber": "string",
"preferredTelephoneExtension": "string"
},
"product": {
"serialNumber": "string",
"productID": "string",
"productSeries": "string",
"platform": "string",
"specialRelease": "string",
"routerName": "string"
}
}
}
{
"createSRResponse": {
"statusCode": "200",
"status": "Success",
"message": "Successfully processed the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string"
}
}
{
"createSRResponse": {
"statusCode": "300",
"status": "Warning",
"message": "Successfully processed the request but there are warnings that need to be looked at.",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"fault": [
{
"errorClass": "Warning",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
{
"createSRResponse": {
"statusCode": "400",
"status": "Error",
"message": "Error in processing the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"fault": [
{
"errorClass": "string",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
updateSR
UpdateSR API enables you to add a Note or modify the Synopsis or Problem Description provided during createSR or change priority, followup method, specialRelease, routerName or overwrite cc email with a new cc list. Multiple attributes of the SR can be updated in one updateSR API call - for example you can change priority and add a note in the same updateSR API request.
Use other APIs to escalate or close an SR, or attach files to the SR.
{
"updateSRRequest": {
"appId": "string",
"userId": "string",
"requestDateTime": "string",
"caseInformation": {
"customerCaseNumber": "string",
"serviceRequestNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string",
"addSenderToEmail": boolean,
"ccEmail": "string",
"followUpMethod": "string",
"networkOutage": boolean,
"synopsis": "string",
"priority": "string",
"problemDescription": "string"
},
"contact": {
"accountID": "string",
"contactEmail": "string",
"preferredTelephoneCountryCode": "string",
"preferredTelephoneNumber": "string",
"preferredTelephoneExtension": "string"
},
"product": {
"specialRelease": "string",
"routerName": "string"
},
"notes": {
"noteTitle": "string",
"content": "string"
}
}
}
{
"updateSRResponse": {
"statusCode": "200",
"status": "Success",
"message": "Successfully processed the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string"
}
}
{
"updateSRResponse": {
"statusCode": "300",
"status": "Warning",
"message": "Successfully processed the request but there are warnings that need to be looked at.",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"fault": [
{
"errorClass": "Warning",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
{
"updateSRResponse": {
"statusCode": "400",
"status": "Error",
"message": "Error in processing the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"fault": [
{
"errorClass": "string",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
escalateSR
Escalate an SR specifying a reason code and including an escalation note.
{
"escalateSRRequest": {
"appId": "string",
"userId": "string",
"requestDateTime": "string",
"caseInformation": {
"customerCaseNumber": "string",
"serviceRequestNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string"
},
"contact": {
"accountID": "string",
"contactEmail": "string"
},
"escalationInformation": {
"code": "string",
"additionalEmail": "string",
"telephoneCountryCode": "string",
"telephoneNumber": "string",
"telephoneExtension": "string"
},
"notes": {
"noteTitle": "string",
"content": "string"
}
}
}
{
"escalateSRResponse": {
"statusCode": "200",
"status": "Success",
"message": "Successfully processed the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string"
}
}
{
"escalateSRResponse": {
"statusCode": "300",
"status": "Warning",
"message": "Successfully processed the request but there are warnings that need to be looked at.",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"fault": [
{
"errorClass": "Warning",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
{
"escalateSRResponse": {
"statusCode": "400",
"status": "Error",
"message": "Error in processing the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"fault": [
{
"errorClass": "string",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
closeSR
closeSR API can be used to provide confirmation to Juniper Service Request Owner to close the SR. If the SR is in a Dispatch status, the SR will be automatically taken to Closed Status otherwise the SR Status moves to Pending Closure and the SR owner will do the needful to close the SR.
{
"closeSRRequest" : {
"appId" : "string",
"userId" : "string",
"requestDateTime" : "string",
"caseInformation" : {
"customerCaseNumber" : "string",
"serviceRequestNumber" : "string",
"customerSourceID" : "string",
"customerUniqueTransactionID" : "string"
},
"contact" : {
"accountID" : "string",
"contactEmail" : "string"
},
"notes" : {
"noteTitle" : "string",
"content" : "string"
}
}
}
{
"closeSRResponse": {
"statusCode": "200",
"status": "Success",
"message": "Successfully processed the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string"
}
}
{
"closeSRResponse": {
"statusCode": "300",
"status": "Warning",
"message": "Successfully processed the request but there are warnings that need to be looked at.",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"fault": [
{
"errorClass": "Warning",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
{
"closeSRResponse": {
"statusCode": "400",
"status": "Error",
"message": "Error in processing the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"fault": [
{
"errorClass": "string",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
updateRMA
Update the carrier and waybill number of RMA defective item when you ship the defective item back to Juniper.
{
"updateRMARequest": {
"appId": "string",
"userId": "string",
"requestDateTime": "string",
"caseInformation": {
"customerCaseNumber": "string",
"serviceRequestNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string"
},
"rma": {
"rmaNumber": "string",
"rmaItem": [
{
"defectiveItemNumber": "string",
"carrierCode": "string",
"trackingNumber": "string"
}
]
},
"contact": {
"accountID": "string",
"contactEmail": "string"
}
}
}
{
"updateRMAResponse": {
"statusCode": "200",
"status": "Success",
"message": "Successfully processed the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"rmaNumber": "string"
}
}
{
"updateRMAResponse": {
"statusCode": "300",
"status": "Warning",
"message": "Successfully processed the request but there are warnings that need to be looked at.",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"rmaNumber": "string",
"fault": [
{
"errorClass": "Warning",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
{
"updateRMAResponse": {
"statusCode": "400",
"status": "Error",
"message": "Error in processing the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"rmaNumber": "string",
"fault": [
{
"errorClass": "string",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
querySRdetails
Request SR details using the CCN and SRID. The response contains SR details, including lists of notes, attachments, RMAs, and linked content, plus the full content of the latest 5 notes.
{
"querySRRequest": {
"appId": "string",
"userId": "string",
"requestDateTime": "string",
"caseInformation": {
"customerCaseNumber": "string",
"serviceRequestNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string"
},
"contact": {
"accountID": "string",
"contactEmail": "string"
}
}
}
{
"querySRResponse": {
"statusCode": "200",
"status": "Success",
"message": "Successfully processed the request",
"customerCaseNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string",
"serviceRequestNumber": "string",
"responseDateTime": "string",
"caseType": {
"caseTypeCode": "string",
"caseTypeDescription": "string"
},
"synopsis": "string",
"problemDescription": "string",
"srStatus": "string",
"priority": "string",
"adminSRType": "string",
"adminSRSubType": "string",
"ccEmail": "string",
"addSenderToEmail": boolean,
"followUpMethod": "string",
"srOwnerFullName": "string",
"srOwnerEmailAddress": "string",
"contact": {
"accountID": "string",
"accountName": "string",
"contactName": "string",
"contactEmail": "string",
"preferredTelephoneCountryCode": "string",
"preferredTelephoneNumber": "string",
"preferredTelephoneExtension": "string"
},
"rma": [
{
"rmaNumber": "string",
"items": [
{
"itemNumber": "string",
"itemType": "string",
"itemStatus": "string"
}
]
}
],
"product": {
"serialNumber": "string",
"productID": "string",
"productSeries": "string",
"platform": "string",
"version": "string",
"release": "string",
"software": "string",
"specialRelease": "string",
"routerName": "string"
},
"escalate": [
{
"description": "string",
"dateTime": "string",
"escalatedBy": "string",
"status": "string"
}
],
"notes": [
{
"id": "string",
"description": "string",
"title": "string",
"originator": "string",
"dateTime": "string"
}
],
"attachments": [
{
"sequenceNumber": "string",
"title": "string",
"sizeInBytes": "string",
"path": "string",
"typeDescription": "string",
"uploadedDate": "string",
"uploadedBy": "string"
}
],
"linkedReferences": [
{
"url": "string",
"referenceId": "string",
"referenceType": "string"
}
],
"recentNotes": [
{
"id": "string",
"dateTime": "string",
"originator": "string",
"content": "string"
}
]
}
}
{
"querySRResponse": {
"statusCode": "400",
"status": "Error",
"message": "Error in processing the request",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"serviceRequestNumber": "string",
"customerSourceID": "string",
"responseDateTime": "string",
"fault": [
{
"errorClass": "string",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
querysrNoteDetails
Request the contents of a note in a SR by SRID and NoteID. The response is note contents for that NoteID in the specified SR.
Note: Bulk extraction of all notes is NOT supported.
{
"querySRNoteRequest": {
"appId": "string",
"userId": "string",
"requestDateTime": "string",
"caseInformation": {
"customerCaseNumber": "string",
"serviceRequestNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string"
},
"noteId": "string",
"contact": {
"accountID": "string",
"contactEmail": "string"
}
}
}
{
"querySRNoteResponse": {
"statusCode": "200",
"status": "Success",
"message": "Successfully processed the request",
"serviceRequestNumber": "string",
"responseDateTime": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"customerSourceID": "string",
"id": "string",
"content": "string",
"dateTime": "string",
}
}
{
"querySRNoteResponse": {
"statusCode": "400",
"status": "Error",
"message": "Error in processing the request",
"serviceRequestNumber": "string",
"responseDateTime": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"customerSourceID": "string",
"fault": [
{
"errorType": "string",
"errorClass": "string",
"errorMessage": "string",
"errorCode": "string"
}
]
}
}
queryRMAdetails
Request RMA details using the CCN, SRID, and RMA number. SRs can have multiple RMAs. You must call queryRMA for each RMA in the SR. The response contains RMA details.
{
"queryRMARequest": {
"appId": "string",
"userId": "string",
"requestDateTime": "string",
"caseInformation": {
"customerCaseNumber": "string",
"serviceRequestNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string"
},
"rmaNumber": "string",
"contact": {
"accountID": "string",
"contactEmail": "string"
}
}
}
{
"queryRMAResponse": {
"statusCode": "200",
"status": "Success",
"message": "Successfully processed the request",
"serviceRequestNumber": "string",
"responseDateTime": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"customerSourceID": "string",
"rmaNumber": "string",
"rmaContact": {
"telephoneCountryCode": "string",
"telephoneNumber": "string",
"address": {
"country": "string",
"address2": "string",
"city": "string",
"address1": "string",
"countryCode": "string",
"postalCode": "string",
"stateCode": "string",
"state": "string"
},
"contactEmail": "string",
"contactName": "string",
"companyName": "string"
}
"defectiveItems": [
{
"dateTime": "string",
"itemNumber": "string",
"carrierDescription": "string",
"serialNumber": "string",
"defectiveItemStatus": "string",
"productID": "string",
"trackingNumber": "string",
"receivedDate": "string"
}
],
"replacementItems": [
{
"receivedBy": "string",
"itemNumber": "string",
"carrierDescription": "string",
"shipmentServiceLevel": "string",
"serialNumber": "string",
"productID": "string",
"defectiveItemNumber": "string",
"replacementStatus": "string",
"shipDate": "string",
"trackingNumber": "string",
"deliveredDate": "string"
}
],
"ceItems": [
{
"defectiveItemNumber": "string",
"productID": "string",
"engineerStatus": "string",
"vendorName": "string",
"vendorPhone": "string",
"serviceRequestedDate": "string",
"actualServicedDate": "string",
"contactedDate": "string",
"estimatedArrivalDate": "string"
}
],
}
}
{
"queryRMAResponse": {
"statusCode": "400",
"status": "Error",
"message": "Error in processing the request",
"serviceRequestNumber": "string",
"responseDateTime": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"customerSourceID": "string",
"rmaNumber": "string",
"fault": [
{
"errorType": "string",
"errorClass": "string",
"errorMessage": "string",
"errorCode": "string"
}
]
}
}
getFileUploadToken
Attaching a file to an SR is a three-step process. First step is to obtain a stsToken from Juniper using this API. The response contains the required token information for the Client to use with AWS S3 SDK to upload files to Juniper's AWS S3 storage (see Amazon's Using The MP Java API documentation.)
{
"fileUploadTokenRequest": {
"appId": "string",
"userId": "string",
"requestDateTime": "string",
"caseInformation": {
"customerCaseNumber": "string",
"serviceRequestNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string"
},
"contact": {
"accountID": "string",
"contactEmail": "string"
}
}
}
{
"fileUploadTokenResponse": {
"statusCode": "200",
"status": "Success",
"message": "Successfully processed the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"stsToken": {
"bucketName": "string",
"path": "string",
"accessKey": "string",
"sessionToken": "string",
"secret": "string",
"region": "string"
}
}
}
{
"fileUploadTokenResponse": {
"statusCode": "400",
"status": "Error",
"message": "Error in processing the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"fault": [
{
"errorType": "string",
"errorClass": "string",
"errorMessage": "string",
"errorCode": "string"
}
]
}
}
attachFile
Pass information about the uploaded files. After successfully uploading the file or files to Juniper's AWS S3 storage, call this API to link the file(s) to the SR for access by Juniper's agents.
{
"attachFileDetailsRequest": {
"appId": "string",
"userId": "string",
"requestDateTime": "string",
"caseInformation": {
"customerCaseNumber": "string",
"serviceRequestNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string"
},
"contact": {
"accountID": "string",
"contactEmail": "string"
},
"attachment": [
{
"title": "string",
"type": "string",
"sizeInBytes": "string",
"documentPath": "string",
"uploadedDateTime": "string"
}
]
}
}
{
"attachFileDetailsResponse": {
"statusCode": "200",
"status": "Success",
"message": "Successfully processed the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string"
}
}
{
"attachFileDetailsResponse": {
"statusCode": "400",
"status": "Error",
"message": "Error in processing the request",
"responseDateTime": "string",
"serviceRequestNumber": "string",
"customerCaseNumber": "string",
"customerUniqueTransactionID": "string",
"fault": [
{
"errorType": "string",
"errorClass": "string",
"errorMessage": "string",
"errorCode": "string"
}
]
}
}
publishSR
Based on certain SR events, Juniper publishes SR details, including list of notes, attachments, RMAs and linked content, plus the full content of the latest 5 notes. The payload is the same as sent in querySR response.
{
"srDetails": {
"statusCode": "string",
"status": "string",
"message": "string",
"appId":"string",
"customerCaseNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string",
"junUniqueTransactionID":"string",
"serviceRequestNumber": "string",
"transactionDateTime": "string",
"srStatus":"string",
"caseType": {
"code": "string",
"description": "string"
},
"synopsis": "string",
"problemDescription": "string",
"priority": "string",
"adminSRType": "string",
"adminSRSubType": "string",
"ccEmail": "string",
"addSenderToEmail": boolean,
"followUpMethod": "string",
"srOwnerFullName": "string",
"srOwnerEmailAddress": "string",
"contact": {
"accountID": "string",
"accountName": "string",
"contactName": "string",
"contactEmail": "string",
"preferredTelephoneCountryCode": "string",
"preferredTelephoneNumber": "string",
"preferredTelephoneExtension": "string"
},
"rma": [
{
"rmaNumber": "string",
"items": [
{
"itemNumber": "string",
"itemType": "string",
"itemStatus": "string"
}
]
}
],
"product": {
"serialNumber": "string",
"productID": "string",
"productSeries": "string",
"platform": "string",
"version": "string",
"release": "string",
"software": "string",
"specialRelease": "string",
"routerName": "string"
},
"escalate": [
{
"description": "string",
"dateTime": "string",
"escalatedBy": "string",
"status": "string"
}
],
"notes": [
{
"id": "string",
"description": "string",
"title": "string",
"originator": "string",
"dateTime": "string"
}
],
"attachments": [
{
"sequenceNumber": "string",
"title": "string",
"sizeInBytes": "string",
"path": "string",
"typeDescription": "string",
"uploadedDate": "string",
"uploadedBy": "string"
}
],
"linkedReferences": [
{
"url": "string",
"referenceId": "string",
"referenceType": "string"
}
],
"recentNotes": [
{
"id": "string",
"dateTime": "string",
"originator": "string",
"content": "string"
}
]
}
}
{
"srDetails": {
"statusCode": "string",
"status": "string",
"message": "string",
"appId":"string",
"customerCaseNumber": "string",
"customerSourceID": "string",
"customerUniqueTransactionID": "string",
"junUniqueTransactionID":"string",
"serviceRequestNumber": "string",
"transactionDateTime": "string",
"fault": [
{
"errorClass": "string",
"errorType": "string",
"errorCode": "string",
"errorMessage": "string"
}
]
}
}
publishLOV
Publishes a pre-defined list of values (LOV) for various keys for Client application to use for composing API requests. publishLOV will be sent to client endpoint on a periodic basis.
List of Values
{
"carrier": [
{
"code": "02",
"description": "DHL",
"carrierTrackingURL": "http://www.dhl.com/en/express/tracking.html"
},
{
"code": "04",
"description": "ESTAFETA",
"carrierTrackingURL": "https://track.aftership.com/estafeta/"
},
{
"code": "05",
"description": "FEDEX",
"carrierTrackingURL": "https://www.fedex.com/apps/fedextrack/?tracknumbers="
},
{
"code": "06",
"description": "UPS",
"carrierTrackingURL": "http://wwwapps.ups.com/WebTracking/track?track=yes&trackNums="
},
{
"code": "07",
"description": "OTHER",
"carrierTrackingURL": "https://www.upspostsaleslogistics.com/cfw/tracking.screen"
},
{
"code": "09",
"description": "HAND-CARRY",
"carrierTrackingURL": "Please contact customercare@juniper.net for additional information"
},
{
"code": "10",
"description": "NFO",
"carrierTrackingURL": "https://www.upspostsaleslogistics.com/cfw/tracking.screen"
},
{
"code": "11",
"description": "EXPEDITORS INTERNATIONAL",
"carrierTrackingURL": "http://www.expeditors.com/"
},
{
"code": "12",
"description": "HAAS",
"carrierTrackingURL": ""
},
{
"code": "17",
"description": "UPS EUROPE",
"carrierTrackingURL": "http://wwwapps.ups.com/WebTracking/track?track=yes&trackNums="
},
{
"code": "18",
"description": "BLUEDART",
"carrierTrackingURL": "http://www.bluedarttrackings.in/"
},
{
"code": "19",
"description": "CAE",
"carrierTrackingURL": "http://www.cae.com.cn"
},
{
"code": "20",
"description": "COURIER POST",
"carrierTrackingURL": "https://www.courierpost.co.nz/track/track-and-trace/"
},
{
"code": "21",
"description": "DIRECT COURIERS",
"carrierTrackingURL": "https://www.directcouriers.com.au/"
},
{
"code": "22",
"description": "EES",
"carrierTrackingURL": "http://www.ees.com.cn/CargoTracing.aspx "
},
{
"code": "23",
"description": "IL-YANG LOGIS",
"carrierTrackingURL": "https://www.ilyanglogis.com/"
},
{
"code": "24",
"description": "INSTANT DELIVERY",
"carrierTrackingURL": "http://idspl.in/"
},
{
"code": "25",
"description": "KINTETSU",
"carrierTrackingURL": "https://cs.kintetsu-ls.co.jp/tr/"
},
{
"code": "26",
"description": "LOCAL COURIER",
"carrierTrackingURL": "https://www.upspostsaleslogistics.com/cfw/tracking.screen"
},
{
"code": "27",
"description": "LOGINTEC",
"carrierTrackingURL": "Please contact customercare@juniper.net for additional information"
},
{
"code": "28",
"description": "NITTSU",
"carrierTrackingURL": "http://www20.nittsu.co.jp/sora/tracetop.htm"
},
{
"code": "29",
"description": "OVERNITE",
"carrierTrackingURL": "http://www.overnitenet.com/"
},
{
"code": "30",
"description": "PRESTO",
"carrierTrackingURL": "Please contact customercare@juniper.net for additional information"
},
{
"code": "31",
"description": "PROCONNECT",
"carrierTrackingURL": "http://proconnectlogistics.com/e-track"
},
{
"code": "32",
"description": "SAFEXPRESS",
"carrierTrackingURL": "http://www.safexpress.com/"
},
{
"code": "33",
"description": "SINOAIR",
"carrierTrackingURL": "http://www.sinoairexpress.com/en/track.htm"
},
{
"code": "34",
"description": "SPOTON",
"carrierTrackingURL": "http://www.spoton.co.in/"
},
{
"code": "35",
"description": "STARTRACK",
"carrierTrackingURL": "https://startrack.com.au/"
},
{
"code": "36",
"description": "TNT",
"carrierTrackingURL": "http://www.tnt.com/express/en_us/site/home/applications/tracking.html?cons="
},
{
"code": "37",
"description": "TOLL",
"carrierTrackingURL": "https://www.mytoll.com/"
},
{
"code": "38",
"description": "UPS AIR FREIGHT",
"carrierTrackingURL": "http://wwwapps.ups.com/WebTracking/track?track=yes&trackNums="
},
{
"code": "39",
"description": "UPS CANADA",
"carrierTrackingURL": "http://wwwapps.ups.com/WebTracking/track?track=yes&trackNums="
},
{
"code": "40",
"description": "UPS SPLUS",
"carrierTrackingURL": "https://www.upspostsaleslogistics.com/cfw/tracking.screen"
},
{
"code": "41",
"description": "LOGI",
"carrierTrackingURL": "Please contact customercare@juniper.net for additional information \n"
},
{
"code": "42",
"description": "EXPEDITORS",
"carrierTrackingURL": "https://www.expeditors.com/"
},
{
"code": "43",
"description": "BLUE DART",
"carrierTrackingURL": "https://www.bluedart.com/tracking"
},
{
"code": "44",
"description": "TNTM",
"carrierTrackingURL": "https://www.tnt.com/"
},
{
"code": "45",
"description": "FLAS",
"carrierTrackingURL": "Please contact customercare@juniper.net for additional information "
},
{
"code": "46",
"description": "SEE INSTRUCTIONS",
"carrierTrackingURL": ""
},
{
"code": "47",
"description": "BRING",
"carrierTrackingURL": "https://www.bring.no/"
},
{
"code": "48",
"description": "NTL",
"carrierTrackingURL": ""
},
{
"code": "49",
"description": "SHL",
"carrierTrackingURL": ""
},
{
"code": "50",
"description": "NSS",
"carrierTrackingURL": ""
},
{
"code": "51",
"description": "TNTN",
"carrierTrackingURL": ""
},
{
"code": "52",
"description": "TNTV",
"carrierTrackingURL": ""
},
{
"code": "53",
"description": "PACE",
"carrierTrackingURL": "https://www.nzpost.co.nz/tools/tracking"
},
{
"code": "54",
"description": "UPS FREIGHT",
"carrierTrackingURL": "http://wwwapps.ups.com/WebTracking/track?track=yes&trackNums="
},
{
"code": "55",
"description": "CSLM",
"carrierTrackingURL": ""
},
{
"code": "56",
"description": "BOLLORE",
"carrierTrackingURL": "https://link.bollore-logistics.com/"
},
{
"code": "58",
"description": "DSL",
"carrierTrackingURL": "Please contact customercare@juniper.net for additional information "
},
{
"code": "59",
"description": "RTT",
"carrierTrackingURL": ""
},
{
"code": "60",
"description": "LOGT",
"carrierTrackingURL": ""
}
],
"attachment": [
{
"value": "Device or Software Configuration",
"key": "CONFIG"
},
{
"value": "Network Topology",
"key": "TOPO"
},
{
"value": "Log, syslog or messages File",
"key": "LOG"
},
{
"value": "Core File",
"key": "CORE"
},
{
"value": "rsi Command Output",
"key": "RSI"
},
{
"value": "Debug File",
"key": "DEBUG"
},
{
"value": "Other Device output",
"key": "OTHER"
},
{
"value": "Screenshot (png, jpg)",
"key": "SCREENSHOT"
},
{
"value": "Word, PPT, Excel, PDF documents",
"key": "DOCUMENT"
}
],
"adminType": [
"Customer Feedback",
"General Inquiry",
"Product Licensing",
"Logistics & RMA",
"Mis-Ship",
"Product Registration",
"Sales Inquiry",
"Warranty & Contracts",
"eLearning",
"TSANet",
"User Access Issues",
"User Account Administration",
"Partner Center Tools",
"Renewal Quotes",
"Support API"
],
"escalation": [
{
"value": "Faster Technical Progress",
"key": "20"
},
{
"value": "Support Engineer Now",
"key": "50"
},
{
"value": "SR Reassignment - Next available engineer (any time zone)",
"key": "61"
},
{
"value": "SR Reassignment - Next available engineer (my time zone)",
"key": "62"
},
{
"value": "Faster RMA Progress - Waiting for RMA to be created",
"key": "71"
},
{
"value": "Faster RMA Progress - Existing RMA",
"key": "72"
}
],
"followUpMethod": [
{
"value": "Email Full Text Update",
"key": "Full"
},
{
"value": "Email Secure Web Link",
"key": "Secure"
}
],
"caseStatus": [
"Closed",
"Open",
"Open - Awaiting Customer Input",
"Pending Closure",
"Pending Closure - Awaiting Customer Input"
],
"platformSeries": {
"Contrail Networking": [
"Contrail Networking"
],
"WANDL": [
"WANDL IP/MPLSView"
],
"BTI-Series": [
"proNX Service Manager",
"proNX 900"
],
"Contrail Service Orchestration": [
"Contrail Service Orchestration"
],
"JUNOS Space": [
"Platform-JA1500",
"Platform-JA2500",
"Platform-Virtual"
],
"Contrail Cloud": [
"Contrail Cloud"
],
"PS Automation Series": [
"Custom Software",
"NITA",
"J-EDI"
],
"WebApp Secure (Formerly Mykonos)": [
"WEBAPP SECURE"
],
"Route Reflectors - JRR/vRR": [
"Virtual Route Reflector"
],
"Z01SPOC": [
"Lenovo",
"Mavenir",
"Red Hat",
"HPE",
"Metaswitch"
]
},
"messages": [
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed.",
"errorCode": "600"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: serialNumber provided is: &1. /nEither serialNumber is invalid or an RMA is already in-progress .",
"errorCode": "601"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: Serial number or Software Support Reference not provided. SN/SSRN is mandatory for Technical SRs.",
"errorCode": "602"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: Service contract has expired for the serial number or software support reference number./n/nSN/SSRN: &1/nService Contract Number: &2/nService SKU: &3/nContract End Date: &4.",
"errorCode": "603"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: userid &1 is not authorized to open a Service Request for SN/SSRN &2. Support for SN/SSRN specified is supported by Juniper Support Specialist Partner./n/nService Contract Number: &3 /nService SKU: &4 /nContract End Date: &5.",
"errorCode": "604"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: Service contract for the serial number or software support reference number has expired. Additionally userid &1 is not authorized to open a Service Request for this SN/SSRN: &2 Contact your Juniper Support Specialist Partner to renew support./n/nService Contract Number: &3 /nService SKU: &4 /nContract End Date: &5.",
"errorCode": "605"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: Serial Number &1 has NO service contract purchased and is also out of warranty.",
"errorCode": "606"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: Serial Number or Software Support Reference Number &1 is currently being processed. Please open Admin SR or Call Juniper Customer Care for assistance.",
"errorCode": "607"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: Service contract for the serial number or software support reference number has a start date in the future. Please open an Admin Case or Call Juniper Customer Care for assistance./n/nSN/SSRN: &1/nService Contract Number: &2/nService SKU: &3/nContract Start Date: &4.",
"errorCode": "608"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: Serial Number &1 has only Active Warranty. Please open Technical SR via other channels for warranty support.",
"errorCode": "609"
},
{
"errorType": "Warning",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Warning: Serial Number &1 has only Active Warranty and maps to Product ID &2 that is a configurable system. Support will be limited to identification of hardware component that has failed.",
"errorCode": "610"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: Serial Number &1 maps to &2. We don't have a record of the SYSTEM in which this part has been installed. Open Service Request using the serial number of the SYSTEM in which it has been installed.",
"errorCode": "611"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: Error encountered opening Technical SR with Serial Number &1. Please retry request passing in the productID or contact Juniper Customer Care for assistance.",
"errorCode": "612"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: serialNumber provided is: &1, productID provided is: &2. /nEither serialNumber is invalid or an RMA is already in-progress OR the productID is invalid.",
"errorCode": "613"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Entitlement Check Failed: serialNumber provided is: &1, productID provided is: &2. /nEither serialNumber is invalid or an RMA is already in-progress OR the productID is not associated with the serialNumber provided.",
"errorCode": "614"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "appId - &1 - and customerSourceID - &2 - combination is not valid.",
"errorCode": "707"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid appId - &1.",
"errorCode": "735"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "More than one contact record found for contactEmail - &1. Please contact Juniper Customer Care.",
"errorCode": "750"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid accountID - &1.",
"errorCode": "751"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "customerSourceID - &1 - and accountID - &2 combination is not valid.",
"errorCode": "752"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "contactEmail - &1 - is not a registered user.",
"errorCode": "753"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "contactEmail - &1 - is not associated to accountID - &2.",
"errorCode": "754"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "userId - &1 - is not associated to accountID - &2.",
"errorCode": "755"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "customerCaseNumber - &1 - is not associated with the specified Account.",
"errorCode": "756"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid serviceRequestNumber - &1.",
"errorCode": "757"
},
{
"errorType": "Warning",
"errorClass": "Validation",
"errorMessage": "Service Request - &1 - is already created for this customerCaseNumber - &2. Since it is open the create request has been treated as an update request and SR - &3 - updated accordingly.",
"errorCode": "758"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "customerCaseNumber - &1 - is not associated with Service Request - &2.",
"errorCode": "759"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "accountID - &1 - is archived. Please contact Juniper Customer Care.",
"errorCode": "760"
},
{
"errorType": "Warning",
"errorClass": "Processing",
"errorMessage": "Service Request - &1 - is locked. Update request has been queued.",
"errorCode": "761"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "customerCaseNumber provided - &1 - has more than one Case/Service Request in Juniper Support system with the same value. Thus please call querysrdetails API with serviceRequestNumber key.",
"errorCode": "763"
}
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid rmaNumber - &1.",
"errorCode": "765"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid defectiveItemNumber - &1.",
"errorCode": "766"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Serial number or Software Support Reference Number (SSRN) - &1 - is invalid. Please contact Juniper Customer Care if you believe the SN/SSRN is a valid one.",
"errorCode": "768"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "More than one contact record found for userId - &1. Please contact Juniper Customer Care.",
"errorCode": "769"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid noteId - &1.",
"errorCode": "770"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "userId - &1 - is not a registered user.",
"errorCode": "771"
},
{
"errorType": "Error",
"errorClass": "Processing",
"errorMessage": "Service Request creation failed for accountID &1 and customerCaseNumber - &2.",
"errorCode": "772"
},
{
"errorType": "Error",
"errorClass": "Processing",
"errorMessage": "Service Request creation failed for customerCaseNumber - &1 and accountID -&2 due to SN/SSRN not passing entitlement check.",
"errorCode": "774"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "rmaNumber - &1 - is not associated with serviceRequestNumber - &2.",
"errorCode": "775"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "RMA - &1 - is already closed. No update allowed.",
"errorCode": "776"
},
{
"errorType": "Warning",
"errorClass": "Validation",
"errorMessage": "RMA - &1 - is locked. Update request has been queued.",
"errorCode": "777"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "serviceRequestNumber - &1 - is not associated with the specified Account.",
"errorCode": "778"
},
{
"errorType": "Success",
"errorClass": "Validation",
"errorMessage": "RMA - &1 - updated successfully.",
"errorCode": "779"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Note ID - &1 - is not associated with serviceRequestNumber - &2.",
"errorCode": "780"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "RMA - &1 - Carrier and Tracking Number update failed.",
"errorCode": "781"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "serviceRequestNumber - &1 - is already closed. No updates allowed.",
"errorCode": "782"
},
{
"errorType": "Warning",
"errorClass": "Processing",
"errorMessage": "networkOutage provided is ignored. This key applies only for Tech SRs with priority of P1 – Critical.",
"errorCode": "783"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid caseTypeCode - &1.",
"errorCode": "784"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "serviceRequestNumber - &1 - already exists for the provided customerCaseNumber - &2 - which is in Closed Status. Resubmit create SR request with a new customerCaseNumber.",
"errorCode": "785"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "contactEmail - &1 - is archived. Please contact Juniper Customer Care.",
"errorCode": "786"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "userId - &1 - is archived. Please contact Juniper Customer Care.",
"errorCode": "787"
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - appId - is not provided.",
"errorCode": 900
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - userId - is not provided.",
"errorCode": 901
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - requestDateTime - is not provided.",
"errorCode": 902
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - requestDateTime - format is incorrect. Please provide it in YYYY-MM-DDTHH:mm:ss.SSSZ format.",
"errorCode": 903
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - caseTypeCode - is not provided.",
"errorCode": 904
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - customerCaseNumber - is not provided.",
"errorCode": 905
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - customerSourceID - is not provided.",
"errorCode": 906
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "appId and customerSourceID combination is not valid.",
"errorCode": 907
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - customerUniqueTransactionID - is not provided.",
"errorCode": 908
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - followUpMethod - is not provided.",
"errorCode": 909
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid followUpMethod value.",
"errorCode": 910
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid caseTypeCode value.",
"errorCode": 911
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - synopsis - is not provided.",
"errorCode": 912
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - priority - is not provided.",
"errorCode": 913
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid priority value.",
"errorCode": 914
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - problemDescription - is not provided.",
"errorCode": 915
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - adminSRType - is not provided for Admin SR.",
"errorCode": 916
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid adminSRType value.",
"errorCode": 917
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - adminSRSubType - is not provided for Admin SR.",
"errorCode": 918
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - accountID - is not provided.",
"errorCode": 919
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - contactEmail - is not provided.",
"errorCode": 920
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - serialNumber - cannot be blank for this productSeries and platform combination.",
"errorCode": 921
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid productSeries value.",
"errorCode": 923
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid platform value.",
"errorCode": 925
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - code - is not provided.",
"errorCode": 926
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - telephoneCountryCode - is not provided.",
"errorCode": 927
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - telephoneNumber - is not provided.",
"errorCode": 928
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - notes - is not provided.",
"errorCode": 929
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - notes - is not provided.",
"errorCode": 930
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - serviceRequestNumber - is not provided.",
"errorCode": 931
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "appId and userId combination is not valid.",
"errorCode": 932
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid adminSRSubType value.",
"errorCode": 933
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid escalation code value.",
"errorCode": 934
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - appId - is invalid.",
"errorCode": 935
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Account Identifier $AccountIdentifier associated with user $user is an incorrect configuration made by Juniper. Please contact Juniper.",
"errorCode": 936
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid authentication method.",
"errorCode": 937
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "User not authenticated with a valid certificate.",
"errorCode": 938
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - noteId - is not provided.",
"errorCode": 942
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - rmaNumber - is not provided.",
"errorCode": 944
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - rmaItem - is not provided.",
"errorCode": 945
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - title - is not provided.",
"errorCode": 946
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - type - is not provided.",
"errorCode": 947
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - sizeInBytes - is not provided.",
"errorCode": 948
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - documentPath - is not provided.",
"errorCode": 949
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - uploadedDateTime - is not provided.",
"errorCode": 950
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - defectiveItemNumber - is not provided.",
"errorCode": 951
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - carrierCode - is not provided.",
"errorCode": 952
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - trackingNumber - is not provided.",
"errorCode": 953
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - serialNumber - cannot be blank for TEC SR.",
"errorCode": 954
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Duplicate customerUniqueTransactionID detected. Please provide an unique transaction ID.",
"errorCode": 955
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Mandatory key - serviceRequestNumber or customerCaseNumber - is needed.",
"errorCode": 956
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid addSenderToEmail value. Only true or false permitted.",
"errorCode": 957
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "Invalid networkOutage value. Only true or false permitted.",
"errorCode": 958
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "A system error has occurred in preparing the response. Please contact Juniper.",
"errorCode": 973
},
{
"errorType": "Error",
"errorClass": "Validation",
"errorMessage": "&jsonkey provided exceeds the maximum allowed &1 characters.",
"errorCode": 999
}
],
"priority": [
"P1 - Critical",
"P2 - High",
"P3 - Medium",
"P4 - Low"
],
"noteDescription": [
"Problem Description",
"Customer Notes",
"Resolution Notes",
"Email Log",
"RMA Notes",
"RMA Notice",
"Current Status"
],
"adminSubType": {
"Partner Center Tools": [
"Learning Academy",
"Deal Registration",
"Password Reset Policy",
"Other"
],
"User Access Issues": [
"J-Net Community",
"Software Downloads",
"Partner Center",
"Order Status Tool",
"MyJuniper",
"Vlabs, EngNet & JCL",
"Support Site",
"Other"
],
"Logistics & RMA": [
"Asset Recovery",
"RMA Expedite",
"No Entitlement",
"RA/FA Request",
"RMA Status",
"Onsite CE Request",
"Other"
],
"Customer Feedback": [
"Customer Care",
"Knowledge Base",
"Juniper.net",
"Juniper Partner Center",
"MyJuniper",
"JTAC",
"Juniper Support Site",
"Other"
],
"Product Registration": [
"Update Registration",
"Grey Market",
"Registration Error",
"Second Hand Purchase",
"Validate Registration",
"Other"
],
"Product Licensing": [
"Installation",
"Renewal Issue",
"Emergency License",
"Not Received",
"Trial / Eval Request",
"Activation Assistance",
"Other"
],
"eLearning": [
"Cert Manager",
"Learning Portal",
"Other"
],
"Support API": [
"Case API"
],
"Mis-Ship": [
"Non-FRU Part Request",
"FRU Part Request",
"Other"
],
"General Inquiry": [
"WEEE Submission",
"Other"
],
"User Account Administration": [
"Edit Account Information",
"Upgrade User Account",
"Change/Reset Password",
"Manage Subscriptions",
"User Registration",
"Other"
],
"Warranty & Contracts": [
"Warranty Status",
"Contract Status",
"3 Legged RMA",
"Contract Expedite",
"PO in Progress",
"Welcome Letter Request",
"Contract Change",
"Other"
],
"TSANet": [
"Basic",
"Premium",
"Limited"
],
"Sales Inquiry": [
"Order Expedite",
"How To Buy",
"Order Status",
"Other"
],
"Renewal Quotes": [
"Error Message",
"Quote Revision",
"Missing Data",
"Quote Downloads",
"Other",
"Request Training"
]
},
"caseType": [
{
"value": "Admin Service Request",
"key": "ADM"
},
{
"value": "Technical Service Request",
"key": "TEC"
}
]
}
getLOV
As an alternative to creating an endpoint and receiving publishLOV messages sent by Juniper on a periodic basis, the getlov API can be used to fetch the applicable List of Values (LOV) for various keys for Client application to use for composing API requests and understanding the various LOVs for some keys in API responses. It is recommended that the LOV data is cached by the client system and the api NOT called frequently as the underlying LOV data changes infrequently. Recommendation is to call this api once a week and update your local cached data.
API is called with Verb GET and with parameter appId
getlov protected url
?appId=replaceWithAppropriateAppID
JSON Keys in API Requests
JSON Key | Data Type | Length | Description | Mandatory or Optional | Comments |
---|---|---|---|---|---|
accountID | CHAR | 10 | Account ID | Mandatory | On createSRAPI request, the contactEmail must be associated with this accountID. This new SR is associated with this accountID. In all other API requests, the contactEmail must be associated with this accountID and must match the accountID in the serviceRequestNumber. |
additionalEmail | CHAR | 255 | Additional persons to notify. | Optional | |
addSenderToEmail | Boolean | 5 | Add Sender to Email Recipients field. | Optional - true or false | |
adminSRSubType | CHAR | 50 | Admin Service Request Sub Type | Admin SRs Only - Mandatory | (Admin SRs only) Acceptable values are in the LOV data. |
adminSRType | CHAR | 50 | Admin Service Request Type | Admin SRs Only - Mandatory | (Admin SRs only) Acceptable values are in the LOV data. |
appId | CHAR | 40 | Handshake API Key | Mandatory | Provided by Juniper during Client onboarding. |
carrierCode | CHAR | 2 | Carrier Code | Mandatory | |
caseTypeCode | CHAR | 4 | Case Type Code | Mandatory | Acceptable values are in the LOV data |
ccEmail | CHAR | 255 | CC Customer Recipients | Update using the updateSR API. Value is overwritten. Cannot be made blank via this Channel. Use the self-service portal if there is a need to clear all entries in this field. |
|
code | CHAR | 2 | Escalate Code | Mandatory | Acceptable values are in the LOV data |
contactEmail | CHAR | 241 | Contact E-Mail Address | Mandatory | This is a registered user of the Client in our Juniper Customer Service Portal. This user must be associated with the accountID. It is expected to be different from the userId and represent the person actually opening the ticket on your support CRM system or updating an existing ticket on your support CRM system. In createSR API requests, this is the SR Reporter on the SR created on the Juniper Support system. Juniper Support engineers expect this to be a real person and not an alias. In updateSR API requests this is recorded as the person making the update. |
content | CHAR | 40000/4000 | Note Text | Optional in updateSR. Mandatory in escalateSR. |
In updateSR the max size of this key is 40,000 characters. In escalateSR the max size of this key is 4000 characters. |
customerCaseNumber | CHAR | 40 | Customer Tracking Number | Mandatory in createSR. Optional in other APIs. |
For existing SRs, it cannot be updated using updateSR API. |
customerSourceID | CHAR | 40 | Customer Source Identifier | Mandatory | Identifier to distinguish the Source within the Client. This is decided during onboarding. This is sent on all Publish SRs. |
customerUniqueTransactionID | CHAR | 40 | Customer Transaction Number | Mandatory | Each request must be a New Unique value. Use to prevent multiple updates of the same transaction. |
defectiveItemNumber | CHAR | 10 | Defective Item No | Mandatory | |
documentPath | CHAR | 500 | See Comments | Mandatory | For example, the complete path to the file (path returned as the part of token response + S3 file name). S3Upload:archive/attachments/2019/XX/XXXX/fileName |
followUpMethod | CHAR | 10 | Follow-Up Method Code | Mandatory in createSR. Optional in updateSR. |
Acceptable values are in the LOV data. Can update using the updateSR API. |
networkOutage | Boolean | Is this a Network Outage? | Optional - true or false | P1 Tech SRs only; otherwise ignored. | |
noteId | CHAR | 70 | Note ID | Mandatory | |
noteTitle | CHAR | 200 | Note Title | Optional | In updateSR when creating a note, specify the title for the note. Similar to 'Subject Line' concept in email. |
platform | CHAR | 50 | Product Platform | Optional | Provide only for Series + Platform exempt from SN input. |
preferredTelephoneCountryCode | CHAR | 2 | Preferred Telephone: ISO 2 character country code | Optional | Example for USA this would US and for France it would be FR. Update using the updateSR API, but cannot be made blank via this Channel. Use the self-service portal if there is a need to clear this field. |
preferredTelephoneExtension | CHAR | 10 | Preferred Telephone: Extension | Optional | Update using the updateSR API, but cannot be made blank via this Channel. Use the self-service portal if there is a need to clear this field. |
preferredTelephoneNumber | CHAR | 30 | Preferred Telephone: Number | Optional | Update using the updateSR API, but cannot be made blank via this Channel. Use the self-service portal if there is a need to clear this field. |
priority | CHAR | 20 | Priority | Mandatory in createSR Optional in updateSR |
Acceptable values are in the LOV data. Update using the updateSR API. |
problemDescription | CHAR | 15000 | Note Text | Mandatory in createSR. Optional in updateSR. |
Update using the updateSR API. |
productID | CHAR | 40 | Product ID | Optional | |
productSeries | CHAR | 50 | Product Series | Optional | Provide only for Series + Platform exempt from SN input. |
requestDateTime | CHAR | 24 | API Request Date Time (in UTC) Format: YYYY-MM-DDTHH:mm:ss.SSSZ |
Mandatory | |
rmaNumber | CHAR | 11 | RMA Number | Mandatory | |
routerName | CHAR | 80 | Router Name | Optional | Update using the updateSR API, but cannot be made blank via this Channel. Use the self-service portal if there is a need to clear this field. |
sizeInBytes | CHAR | 100 | File size in bytes | Mandatory | No validation done if the value provided is a number. |
serialNumber | CHAR | 18 | Product Serial Number or Software Support Reference Number (SSRN) | Optional for Admin SRs. Mandatory for Tech SRs except for Series + Platform exempt from SN input. |
Exempt Series + Platform provided in the LOV data. |
serviceRequestNumber | CHAR | 16 | Juniper Service Request ID | Optional in querySR and Mandatory in all API requests that has this key in the request specification. | |
specialRelease | CHAR | 40 | Special Release | Optional | Update using the updateSR API, but cannot be made blank via this Channel. Use the self-service portal if there is a need to clear this field. |
synopsis | CHAR | 250 | Synopsis of the service request | Mandatory in createSR. Optional in updateSR. |
Update using the updateSR API. |
telephoneCountryCode | CHAR | 2 | Telephone: ISO 2 character country code | Mandatory | |
telephoneExtension | CHAR | 10 | Telephone: Extension | Optional | |
telephoneNumber | CHAR | 30 | Telephone: Number | Mandatory | |
title | CHAR | 500 | Filename or description. | Mandatory | |
trackingNumber | CHAR | 20 | Waybill Number | Mandatory | |
type | CHAR | 10 | Type of File | Mandatory | Acceptable value in the LOV. If value provided does not match from acceptable list, it defaults to DOCUMENT type. |
uploadedDateTime | CHAR | 24 | In UTC. Format: YYYY-MM-DDTHH:mm:ss.SSSZ | Mandatory | Indicates the timestamp of the file uploaded to AWS S3. This is used by Juniper for reference only. |
userId | CHAR | 241 | Registered userid | Mandatory | The userId is a mandatory key on each of the 10 SR API requests. It must be a registered user on Juniper’s Customer Service Portal. It must match that provided during Client onboarding. |
JSON Keys in API Responses, Publish SR
accessKey | CHAR | 128 | A key to use with the AWS S3 SDK. | |
accountName | CHAR | 160 | Account Name | |
actualServicedDate | CHAR | 24 | Actual arrival date. | |
address1 | CHAR | 60 | Ship To Address Line 1 | |
address2 | CHAR | 60 | Ship To Address Line 2 | |
addSenderToEmail | CHAR | 5 | Add sender (Inbound Email Address) to email recipients field | Either true or false |
adminSRSubType | CHAR | 50 | Admin SR Sub Type | Admin SR only. |
adminSRType | CHAR | 50 | Admin service request type. | Admin SR only. |
bucketName | CHAR | 63 | A key to use with the AWS S3 SDK. | |
carrierDescription | CHAR | 60 | Carrier | |
caseTypeCode | CHAR | 4 | Case type code. | |
caseTypeDescription | CHAR | 40 | Case type description. | |
ccEmail | CHAR | 255 | CC Customer recipients. | |
city | CHAR | 40 | Ship To City | |
companyName | CHAR | 160 | Ship To Company Name | |
contact | CHAR | 160 | Ship To Contact Name | |
contactedDate | CHAR | 24 | Contact date. | |
contactEmail | CHAR | 241 | Contact eMail address. In the queryRMA response this is Ship To Contact Email addresses |
|
contactName | CHAR | 80 | Contact Name | |
content | String | Note text. | ||
country | CHAR | 60 | Ship To Country Name | |
countryCode | CHAR | 2 | Ship To Country Code provided as an ISO 2-character country code. | |
customerCaseNumber | CHAR | 40 | Customer Tracking Number | As provided in the API request. |
customerSourceID | CHAR | 40 | Customer Source Identifier | As provided in the API request. |
customerUniqueTransactionID | CHAR | 40 | Customer Transaction Number | As provided in the API request. |
dateTime | CHAR | 24 | In UTC format: YYYY-MM-DDTHH:mm:ss.SSSZ | Refers to the defective item create date. |
defectiveItemNumber | CHAR | 10 | Defective Item No | |
defectiveItemStatus | CHAR | 30 | Defective Item Status | |
description | CHAR | 60 | Escalation description or note type description. | |
engineerStatus | CHAR | 30 | CE Item Status | |
errorClass | CHAR | 15 | Indicates the error class. | Error/Warning |
errorType | CHAR | 15 | Indicates the error type. | Validation/Processing |
errorCode | CHAR | Indicates the fault code. | 4 | |
errorMessage | CHAR | 1000 | Error message description. | |
escalatedBy | CHAR | 160 | Name of the person who initiated the escalation. | |
estimatedArrivalDate | CHAR | 24 | Estimated Arrival Date | |
followUpMethodDescription | CHAR | 40 | Follow-Up Method Description | |
id | CHAR | 70 | Note ID | The note ID is unique for each SR. |
itemNumber | CHAR | 10 | RMA Line Item Number | |
itemStatus | CHAR | 30 | RMA Line Item Status | |
itemType | CHAR | 40 | RMA Line Item Type (Defective, Replacement) | |
junUniqueTransactionID | CHAR | 40 | Juniper Unique Transaction ID | |
message | CHAR | 100 | Status code description. | |
originator | CHAR | 160 | Note originator. | |
path | CHAR | 500 | Path of the attachment. | |
platform | CHAR | 50 | Product platform. | |
postalCode | CHAR | 10 | Ship To Postal Code. | |
preferredTelephoneCountryCode | CHAR | 2 | Preferred Telephone: ISO 2 character country code. | |
preferredTelephoneExtension | CHAR | 10 | Preferred Telephone: Extension | |
preferredTelephoneNumber | CHAR | 30 | Preferred Telephone: Number | |
priority | CHAR | 20 | Priority description. | |
problemDescription | CHAR | 15000 | Problem description. | |
productID | CHAR | 40 | Product ID | |
productSeries | CHAR | 50 | Product Series | |
receivedBy | CHAR | 255 | POD Signed by. | |
receivedDate | CHAR | 24 | Received Date (in UTC) (for defective received by Juniper). Proof of Delivery Date (for replacement delivered to Client). |
|
referenceId | CHAR | 10 | Reference ID | |
referenceType | CHAR | 20 | Reference Type | Indicates type of content source such as PR, KB etc. |
region | CHAR | 15 | A key to use with the AWS S3 SDK. | |
release | CHAR | 30 | Release | |
replacementStatus | CHAR | 30 | Replacement Item Status | |
responseDateTime | CHAR | 24 | Response Date Time (in UTC) Format: YYYY-MM-DDTHH:mm:ss.SSSZ |
As provided in the API request. |
rmaNumber | CHAR | 11 | RMA Number | |
routerName | CHAR | 80 | Router Name | |
secret | CHAR | 128 | A key to use with the AWS S3 SDK. | |
sequenceNumber | CHAR | 10 | A number internal to the attached file. Provided only for troubleshooting purposes. | |
serialNumber | CHAR | 18 | Product Serial Number or Software Support Reference Number (SSRN) | |
serviceRequestedDate | CHAR | 24 | Requested Service Date | |
serviceRequestNumber | CHAR | 16 | Juniper Service Request ID | Will be as provided in the API Request. (Null in CreateSR Response). |
sessionToken | CHAR | 5000 | A key to use with the AWS S3 SDK. | |
shipDate | CHAR | 24 | Ship Date (in UTC) | |
shipmentServiceLevel | CHAR | 40 | Shipment Service Level | |
sizeInBytes | CHAR | 100 | Size of the attachment in bytes. | |
software | CHAR | 60 | Software | |
specialRelease | CHAR | 40 | Special Release | |
srOwnerEmailAddress | CHAR | 241 | Email Address of the Case/SR Owner | |
srOwnerFullName | CHAR | 80 | Name of the Case/SR owner | |
srStatus | CHAR | 60 | SR status description. | |
state | CHAR | 60 | Ship To State, Province, Region Name | |
stateCode | CHAR | 3 | Ship To State, Province, Region Code | |
status | CHAR | 20 | Success or Warning or Error | |
statusCode | CHAR | 4 | 200 for success, 300 for warning, 400 for error | |
synopsis | CHAR | 250 | Synopsis of the SR. | |
telephoneCountryCode | CHAR | 2 | ISO 2 character country Code for Ship To Contact Phone Number. | |
telephoneNumber | CHAR | 30 | Ship To Contact Phone Number | |
title | CHAR | 200 | Note Title | |
title | CHAR | 500 | Attachment filename. | |
trackingNumber | CHAR | 20 | Defective Item Tracking Number | |
trackingNumber | CHAR | 40 | Shipment Tracking Number | |
typeDescription | CHAR | 60 | Attachment Type Description. | String associated with the type code. Refer to LOV table for the various type codes. |
uploadedBy | CHAR | 80 | File uploaded by | |
uploadedDate | CHAR | 24 | File upload timestamp in UTC format: YYYY-MM-DDTHH:mm:ss.SSSZ. | This datetime stamp refers to when the file deposited at AWS S3 is linked to the SR. |
url | CHAR | 255 | Hyperlink to the reference. | |
vendorName | CHAR | 255 | CE Vendor Name | |
vendorPhone | CHAR | 40 | CE Vendor Phone | |
version | CHAR | 20 | Version |
Error Messages
errorType | errorClass | errorCode | errorMessage |
---|---|---|---|
Error | Validation | 600 | Entitlement Check Failed. |
Error | Validation | 601 | Entitlement Check Failed: serialNumber provided is: &1. Either serialNumber is invalid or an RMA is already in-progress. |
Error | Validation | 602 | Entitlement Check Failed: Serial number or Software Support Reference not provided. SN/SSRN is mandatory for Technical SRs. |
Error | Validation | 603 | Entitlement Check Failed: Service contract has expired for the serial number or software support reference number. SN/SSRN: &1 Service Contract Number: &2 Service SKU: &3 Contract End Date: &4. |
Error | Validation | 604 | Entitlement Check Failed: userid &1 is not authorized to open a Service Request for SN/SSRN &2. Support for SN/SSRN specified is supported by Juniper Support Specialist Partner. Service Contract Number: &3 Service SKU: &4 Contract End Date: &5. |
Error | Validation | 605 | Entitlement Check Failed: Service contract for the serial number or software support reference number has expired. Additionally userid &1 is not authorized to open a Service Request for this SN/SSRN: &2 Contact your Juniper Support Specialist Partner to renew support. Service Contract Number: &3 Service SKU: &4 Contract End Date: &5. |
Error | Validation | 606 | Entitlement Check Failed: Serial Number &1 has NO service contract purchased and is also out of warranty. |
Error | Validation | 607 | Entitlement Check Failed: Serial Number or Software Support Reference Number &1 is currently being processed. Please open Admin SR or Call Juniper Customer Care for assistance. |
Error | Validation | 608 | Entitlement Check Failed: Service contract for the serial number or software support reference number has a start date in the future. Please open an Admin Case or Call Juniper Customer Care for assistance. SN/SSRN: &1 Service Contract Number: &2 Service SKU: &3 Contract Start Date: &4. |
Error | Validation | 609 | Entitlement Check Failed: Serial Number &1 has only Active Warranty. Please open Technical SR via other channels for warranty support. |
Warning | Validation | 610 | Entitlement Check Warning: Serial Number &1 has only Active Warranty and maps to Product ID &2 that is a configurable system. Support will be limited to identification of hardware component that has failed. |
Error | Validation | 611 | Entitlement Check Failed: Serial Number &1 maps to &2. We don't have a record of the SYSTEM in which this part has been installed. Open Service Request using the serial number of the SYSTEM in which it has been installed. |
Error | Validation | 612 | Entitlement Check Failed: Error encountered opening Technical SR with Serial Number &1. Please retry request passing in the productID or contact Juniper Customer Care for assistance. |
Error | Validation | 613 | Entitlement Check Failed: serialNumber provided is: &1, productID provided is: &2. Either serialNumber is invalid or an RMA is already in-progress OR the productID is invalid. |
Error | Validation | 614 | Entitlement Check Failed: serialNumber provided is: &1, productID provided is: &2. Either serialNumber is invalid or an RMA is already in-progress OR the productID is not associated with the serialNumber provided. |
Error | Validation | 707 | appId - &1 - and customerSourceID - &2 - combination is not valid. |
Error | Validation | 735 | Invalid appId - &1. |
Error | Validation | 750 | More than one contact record found for contactEmail - &1. Please contact Juniper Customer Care. |
Error | Validation | 751 | Invalid accountID - &1. |
Error | Validation | 752 | customerSourceID - &1 - and accountID - &2 combination is not valid. |
Error | Validation | 753 | contactEmail - &1 - is not a registered user. |
Error | Validation | 754 | contactEmail - &1 - is not associated to accountID - &2. |
Error | Validation | 755 | userId - &1 - is not associated to accountID - &2. |
Error | Validation | 756 | customerCaseNumber - &1 - is not associated with the specified Account. |
Error | Validation | 757 | Invalid serviceRequestNumber - &1. |
Warning | Validation | 758 | Service Request - &1 - is already created for this customerCaseNumber - &2. Since it is open the create request has been treated as an update request and SR - &3 - updated accordingly. |
Error | Validation | 759 | customerCaseNumber - &1 - is not associated with Service Request - &2. |
Error | Validation | 760 | accountID - &1 - is archived. Please contact Juniper Customer Care. |
Warning | Processing | 761 | Service Request - &1 - is locked. Update request has been queued. |
Error | Validation | 763 | customerCaseNumber provided - &1 - has more than one Case/Service Request in Juniper Support system with the same value. Thus please call querysrdetails API with serviceRequestNumber key. |
Error | Validation | 765 | Invalid rmaNumber - &1. |
Error | Validation | 766 | Invalid defectiveItemNumber - &1. |
Error | Validation | 768 | Serial number or Software Support Reference Number (SSRN) - &1 - is invalid. Please contact Juniper Customer Care if you believe the SN/SSRN is a valid one. |
Error | Validation | 769 | More than one contact record found for userId - &1. Please contact Juniper Customer Care. |
Error | Validation | 770 | Invalid noteId - &1. |
Error | Validation | 771 | userId - &1 - is not a registered user. |
Error | Processing | 772 | Service Request creation failed for accountID &1 and customerCaseNumber - &2. |
Error | Processing | 774 | Service Request creation failed for customerCaseNumber - &1 and accountID -&2 due to SN/SSRN not passing entitlement check. |
Error | Validation | 775 | rmaNumber - &1 - is not associated with serviceRequestNumber - &2. |
Error | Validation | 776 | RMA - &1 - is already closed. No update allowed. |
Warning | Validation | 777 | RMA - &1 - is locked. Update request has been queued. |
Error | Validation | 778 | serviceRequestNumber - &1 - is not associated with the specified Account. |
Success | Validation | 779 | RMA - &1 - updated successfully. |
Error | Validation | 780 | Note ID - &1 - is not associated with serviceRequestNumber - &2. |
Error | Validation | 781 | RMA - &1 - Carrier and Tracking Number update failed. |
Error | Validation | 782 | serviceRequestNumber - &1 - is already closed. No updates allowed. |
Warning | Processing | 783 | networkOutage provided is ignored. This key applies only for Tech SRs with priority of P1 – Critical. |
Error | Validation | 784 | Invalid caseTypeCode - &1. |
Error | Validation | 785 | serviceRequestNumber - &1 - already exists for the provided customerCaseNumber - &2 - which is in Closed Status. Resubmit create SR request with a new customerCaseNumber. |
Error | Validation | 786 | contactEmail - &1 - is archived. Please contact Juniper Customer Care. |
Error | Validation | 787 | userId - &1 - is archived. Please contact Juniper Customer Care. |
Error | Validation | 900 | Mandatory key - appId - is not provided. |
Error | Validation | 901 | Mandatory key - userId - is not provided. |
Error | Validation | 902 | Mandatory key - requestDateTime - is not provided. |
Error | Validation | 903 | Mandatory key - requestDateTime - format is incorrect. Please provide it in YYYY-MM-DDTHH:mm:ss.SSSZ format. |
Error | Validation | 904 | Mandatory key - caseTypeCode - is not provided. |
Error | Validation | 905 | Mandatory key - customerCaseNumber - is not provided. |
Error | Validation | 906 | Mandatory key - customerSourceID - is not provided. |
Error | Validation | 907 | appId and customerSourceID combination is not valid. |
Error | Validation | 908 | Mandatory key - customerUniqueTransactionID - is not provided. |
Error | Validation | 909 | Mandatory key - followUpMethod - is not provided. |
Error | Validation | 910 | Invalid followUpMethod value. |
Error | Validation | 911 | Invalid caseTypeCode value. |
Error | Validation | 912 | Mandatory key - synopsis - is not provided. |
Error | Validation | 913 | Mandatory key - priority - is not provided. |
Error | Validation | 914 | Invalid priority value. |
Error | Validation | 915 | Mandatory key - problemDescription - is not provided. |
Error | Validation | 916 | Mandatory key - adminSRType - is not provided for Admin SR. |
Error | Validation | 917 | Invalid adminSRType value. |
Error | Validation | 918 | Mandatory key - adminSRSubType - is not provided for Admin SR. |
Error | Validation | 919 | Mandatory key - accountID - is not provided. |
Error | Validation | 920 | Mandatory key - contactEmail - is not provided. |
Error | Validation | 921 | Mandatory key - serialNumber - cannot be blank for this productSeries and platform combination. |
Error | Validation | 923 | Invalid productSeries value. |
Error | Validation | 925 | Invalid platform value. |
Error | Validation | 926 | Mandatory key - code - is not provided. |
Error | Validation | 927 | Mandatory key - telephoneCountryCode - is not provided. |
Error | Validation | 928 | Mandatory key - telephoneNumber - is not provided. |
Error | Validation | 929 | Mandatory key - notes - is not provided. |
Error | Validation | 930 | Mandatory key - notes - is not provided. |
Error | Validation | 931 | Mandatory key - serviceRequestNumber - is not provided. |
Error | Validation | 932 | appId and userId combination is not valid. |
Error | Validation | 933 | Invalid adminSRSubType value. |
Error | Validation | 934 | Invalid escalation code value. |
Error | Validation | 935 | Mandatory key - appId - is invalid. |
Error | Validation | 936 | Account Identifier $AccountIdentifier associated with user $user is an incorrect configuration made by Juniper. Please contact Juniper. |
Error | Validation | 937 | Invalid authentication method. |
Error | Validation | 938 | User not authenticated with a valid certificate. |
Error | Validation | 942 | Mandatory key - noteId - is not provided. |
Error | Validation | 944 | Mandatory key - rmaNumber - is not provided. |
Error | Validation | 946 | Mandatory key - title - is not provided. |
Error | Validation | 947 | Mandatory key - type - is not provided. |
Error | Validation | 948 | Mandatory key - sizeInBytes - is not provided. |
Error | Validation | 949 | Mandatory key - documentPath - is not provided. |
Error | Validation | 950 | Mandatory key - uploadedDateTime - is not provided. |
Error | Validation | 951 | Mandatory key - defectiveItemNumber - is not provided. |
Error | Validation | 952 | Mandatory key - carrierCode - is not provided. |
Error | Validation | 953 | Mandatory key - trackingNumber - is not provided. |
Error | Validation | 954 | Mandatory key - serialNumber - cannot be blank for TEC SR. |
Error | Validation | 955 | Duplicate customerUniqueTransactionID detected. Please provide an unique transaction ID. |
Error | Validation | 956 | Mandatory key - serviceRequestNumber or customerCaseNumber - is needed. |
Error | Validation | 957 | Invalid addSenderToEmail value. Only true or false permitted. |
Error | Validation | 958 | Invalid networkOutage value. Only true or false permitted. |
Error | Validation | 973 | A system error has occurred in preparing the response. Please contact Juniper. |
Error | Validation | 999 | &jsonkey provided exceeds the maximum allowed &1 characters. |