openapi: 3.1.0 info: title: Shipments Address Parcel Documents API version: 3.0.0 description: The Shipments API allows you to create and announce, retrieve, and cancel outgoing shipments and their associated parcels within the Sendcloud platform. contact: name: Sendcloud API Support email: contact@sendcloud.com license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html servers: - url: https://panel.sendcloud.sc/api/v3 description: Sendcloud Production tags: - name: Parcel Documents paths: /parcels/{id}/documents/{type}: parameters: - $ref: '#/components/parameters/id' - $ref: '#/components/parameters/type' get: summary: Retrieve parcel documents x-mint: href: /api/v2/parcel-documents/retrieve-parcel-documents content: "\n **API v2 is entering maintenance mode.** New users should start with API v3 to access our latest features and improved performance. Already using v2? Don't worry, your current integration remains fully functional. Read more about [maintenance mode](/docs/getting-started/api-version-guide), or check out the [migration guide for API v3](/docs/getting-started/migration-guidelines-for-api-v3).\n\n\nFor international shipments, a commercial invoice, CN23 or CN22 (+CP71) form must be attached (either physically or [digitally](https://support.sendcloud.com/hc/en-us/articles/4417349714452-Send-your-customs-documents-digitally-via-Paperless-Trade-) for some carriers) to the shipment for customs officials to access. The type of document required depends on the shipping method and value of the shipment.\n\nWhen you use the [Create a parcel or parcels](/api/v2/parcels/create-a-parcel-or-parcels) endpoint, Sendcloud generates the correct type of document for your shipment if you have filled in all the information related to the parcel contents, value, and invoice. Use this endpoint to retrieve these documents in your preferred format.\n\nThe supported document types are as follows:\n\n- `air-waybill`\n- `cn23`\n- `cn23-default`\n- `commercial-invoice`\n- `cp71`\n- `label`\n- `qr`" description: Retrieve a document for a given parcel by providing the parcel `id` and document `type`. tags: - Parcel Documents responses: '200': description: Requested parcel document file content: application/pdf: schema: type: string format: binary application/zpl: schema: type: string format: binary image/png: schema: type: string format: binary '404': description: Document type requested is not available for the parcel content: application/json: schema: type: object properties: error: type: object properties: code: type: integer description: HTTP error code example: 404 request: type: string description: Endpoint URL that was requested example: api/v2/parcels/1/documents/commercial-invoice message: type: string description: A human readable error message example: No Parcel matches the given query. examples: NotFound: summary: Parcel Document Not Found value: error: code: 404 request: api/v2/parcels/1/documents/commercial-invoice message: No Parcel matches the given query. document_type_not_found: summary: Document Type Not Found value: error: code: 404 request: api/v2/parcels/1/documents/not-existing-document-type message: Not found. operationId: sc-public-v2-scp-get-retrieve_parcel_documents security: - HTTPBasicAuth: [] - OAuth2ClientCreds: [] parameters: - $ref: '#/components/parameters/dpi' - $ref: '#/components/parameters/rendering_format' - $ref: '#/components/parameters/raw' /parcel-documents/{type}: get: summary: Retrieve multiple parcel documents tags: - Parcel Documents x-mint: href: /api/v3/parcel-documents/retrieve-multiple-parcel-documents content: "Sendcloud generates the correct type of document for your shipment when you [Create a parcel](/api/v2/parcels/create-a-parcel-or-parcels), provided that you have filled in all the information related to the parcel contents, value and invoice. Use this endpoint to retrieve these documents in bulk. \n\nThis endpoint supports the following document types:\n \n - `label`\n - `customs-declaration`\n - `air-waybill`\n\n\n For international shipments, customs declaration must be attached (either physically or [digitally](https://support.sendcloud.com/hc/en-us/articles/4417349714452-Send-your-customs-documents-digitally-via-Paperless-Trade-) for some carriers) to the shipment for customs officials to access.\n" responses: '200': description: Requested parcel document files of a specific type. content: application/pdf: schema: type: string format: binary application/zpl: schema: type: string format: binary image/png: schema: type: string format: binary '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/errors' examples: InvalidType: value: errors: - code: invalid status: '400' detail: Invalid document type. '404': description: Not Found content: application/json: schema: $ref: '#/components/schemas/errors' examples: NotFound: value: errors: - code: not_found status: '404' detail: No Parcel matches the given query. operationId: sc-public-v3-scp-get-retrieve_parcel_documents_bulk security: - HTTPBasicAuth: [] - OAuth2ClientCreds: [] parameters: - $ref: '#/components/parameters/parcels' - $ref: '#/components/parameters/type_2' - $ref: '#/components/parameters/paper-size' description: Download multiple parcel documents of the same type in bulk. components: parameters: paper-size: in: query name: paper_size description: 'The paper size of the document you would like to retrieve. Paper size can be one of: - A4 - A5 - A6 Omitting this query parameter leads to the internal paper size of the document being used. Generally this is A6 for labels and A4 for larger documents, like customs documents. ' schema: type: string enum: - A4 - A5 - A6 example: A4 raw: name: raw in: query required: false schema: type: boolean description: There have been identified cases where custom documents, internally rendered, will only include some of the necessary information, mainly due to some restrictions. Using the raw query param, one can request to receive the document in the originally received format by the carrier. This temporary solution to the problem allows the normal operations of the affected customers. As such, you can expect this property to be sunsetted shortly once the necessary changes have been implemented. parcels: name: parcels in: query required: true schema: type: array items: type: integer example: - 1 - 2 - 3 maxItems: 20 minItems: 1 description: Parcels for which you want to retrieve the documents type: name: type in: path schema: type: string example: commercial-invoice enum: - air-waybill - cn23 - cn23-default - commercial-invoice - cp71 - label - qr description: Document type you want to retrieve for this parcel required: true type_2: name: type in: path schema: type: string example: customs-declaration enum: - label - customs-declaration - air-waybill description: Document type you want to retrieve. required: true rendering_format: name: Accept in: header required: false schema: type: string default: application/pdf enum: - application/pdf - application/zpl - image/png example: image/png description: The returned format of the document id: name: id in: path schema: type: integer example: 1 minimum: 1 description: Identifier of the parcel which you want to retrieve a document from required: true dpi: name: dpi in: query required: false schema: type: integer default: 72 enum: - 72 - 150 - 203 - 300 - 600 example: 300 minimum: 1 description: "DPI refers to the printing resolution of your shipping labels. It's important that labels are printed at a high enough resolution to ensure the clarity of address details and the barcode for scanning purposes.\nUse following amounts for appropriate result:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
File formatDefault DPIValid DPI
pdf7272
png300150, 300
\nZPL labels are not affected by the DPI setting, as the resolution is determined by the carrier itself. Most carriers use a resolution of 203 DPI. Zebra printers need to be configured to print at the specific DPI of the label if they have higher resolution capabilities.\n" schemas: errors: title: Errors type: object description: A standardized format for errors in JSON:API responses. properties: errors: type: - array - object items: type: object allOf: - $ref: '#/components/schemas/ErrorObject' required: - status - code - detail ErrorObject: title: Error type: object description: Error in a JSON:API error format properties: id: type: string description: A unique identifier for the error. links: type: object description: A set of hyperlinks that provide additional information about the error. properties: about: type: string description: A URL that provides additional information about the error. status: type: string format: int32 description: The HTTP status code of the error. minLength: 1 code: type: string description: A unique error code for the error, in snake case format. minLength: 1 enum: - unknown_field - invalid - forbidden - invalid_choice - min_value - 'null' - not_found - required - not_a_list - non_field_errors - authentication_failed - validation_error - parcel_announcement_error title: type: string description: A short, human-readable summary of the error. minLength: 1 detail: type: string description: A human-readable explanation of the error. minLength: 1 source: type: object description: An object that identifies the source of the error within the request payload. properties: pointer: type: string description: A `JSON` pointer to the location of the error within the request payload. parameter: type: string description: The name of the `query` parameter that caused the error. header: type: string description: The name of the `header` parameter that caused the error. meta: type: object description: Additional metadata about the error. securitySchemes: HTTPBasicAuth: type: http description: Basic Authentication using API key and secrets is currently the main authentication mechanism. scheme: basic OAuth2ClientCreds: type: oauth2 description: OAuth2 is a standardized protocol for authorization that allows users to share their private resources stored on one site with another site without having to provide their credentials. OAuth2 Client Credentials Grant workflow. This workflow is typically used for server-to-server interactions that require authorization to access specific resources. flows: clientCredentials: tokenUrl: https://account.sendcloud.com/oauth2/token/ scopes: api: Default OAuth scope required to access Sendcloud API.