Responses

After the service successfully connects with the client request, it sends a response back to the client. An HTTP response code of 200 indicates that the service was able to process the request and the client should continue to parse the response message to determine the transaction status. All other HTTP response codes indicate a problem with the request or connection.

Table: HTTP response codes

Response code

Description

200

OK

400

Bad Request

401

Unauthorized

403

Forbidden

404

Not found

405

Method Not Allowed

408

Request Timeout

500

Internal Server Error

503

Service Unavailable

For valid 200 HTTP responses, the content-type will be text/xml. The response message block will be in XML or JSON (for reporting services).

Depending on whether the transaction is successful, two types of response messages are returned:

Success response:

java
<Response xmlns="urn:symantec:api">
<StatusCode>[Status Code]</StatusCode>
<Message>Description</Message>
[Additional Info]...
</Response>
java
<Error xmlns="urn:symantec:api">
<StatusCode>[Status Code]</StatusCode>
<Message>Description</Message>
</Error>

We use cookies to ensure that we give you the best experience on our website. By using this site, you agree to the Terms of Service.