Edit in GitHubLog an issue

Handling errors

Consider these tips when handling errors.

Complete processing failure#

All HTTP 4xx errors contain a JSON payload with the following structure:

Copied to your clipboard
1{
2 "code" : 1208,
3 "message" : "Insufficient information for Technical Submission"
4}

Batch processing#

Unless there was a complete failure in processing a batch request, a batch response always returns an overall HTTP 200 response code. However, each item in the batch array contains a code and message pair indicating its specific pass/fail result.

  • a code of 200 indicates successful processing of the item
  • a non-200 code indicates an error occurred while attempting to process the item
Copied to your clipboard
1// the overall HTTP response code will be a 200 ...
2[
3 {
4 // ... however each subsection of the batch response might have a non-200 error code
5 "code" : 1208,
6 "message" : "Insufficient information for Technical Submission"
7 },
8 {
9 "code" : 1210,
10 "message" : "Invalid SKU given. SKU must be of the form 'vendor_name/package_name'"
11 },
12 {
13 "code" : 200,
14 "message" : "Success",
15 // ... etc. Successful batch submissions also have all the fields from a successful result.
16 }
17]
  • Privacy
  • Terms of Use
  • Do not sell my personal information
  • AdChoices
Copyright © 2022 Adobe. All rights reserved.