AttachmentsDownload attachment

Download attachment

Downloads the binary content of a transaction attachment. Attachment IDs are returned in each transaction’s attachments array in the card statement response.

Supported formats:

  • image/png — screenshots, photos
  • image/jpeg — photos, scanned receipts
  • application/pdf — invoices, documents

Attachments uploaded as spreadsheets or financial exchange files (XLS, XLSX, ODF, OFX — see CreateAttachmentFileInput.contentType) can also be downloaded; the response Content-Type reflects the original file format.

Download behavior is the same regardless of the attachment's status (PROCESSING or AVAILABLE).

See also: Best practices — Attachments for download examples.

curl -X GET "https://api-sandbox.contasimples.com/attachments/v1/content/example_string" \
  -H "Content-Type: application/json" \
  -H "Signature-Input: example_string" \
  -H "Signature: example_string" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{}
GET
/attachments/v1/content/{attachmentId}
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN

Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN
path
attachmentIdstring
Required

Unique attachment ID, from the attachments array in the card statement response.

header
Signature-Inputstring

What was signed and the signature parameters, in the RFC 9421 format. A credential with a public key must send it on every call, reads included, or the request is refused with 401. The signature covers the @method, @path, and @query components, and also content-digest when there is a body. created and alg are required, and created is valid for 300 seconds. The full format, with examples, is in Request Signing.

header
Signaturestring

The signature of the base defined by RFC 9421, in base64, between : and under the same label used in Signature-Input, for example sig=:SGVsbG8gd29ybGQ=:. It always goes together with Signature-Input.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN

Path Parameters

attachmentIdstring
Required

Unique attachment ID, from the attachments array in the card statement response.

Headers

Signature-Inputstring

What was signed and the signature parameters, in the RFC 9421 format. A credential with a public key must send it on every call, reads included, or the request is refused with 401. The signature covers the @method, @path, and @query components, and also content-digest when there is a body. created and alg are required, and created is valid for 300 seconds. The full format, with examples, is in Request Signing.

Signaturestring

The signature of the base defined by RFC 9421, in base64, between : and under the same label used in Signature-Input, for example sig=:SGVsbG8gd29ybGQ=:. It always goes together with Signature-Input.

Responses

Binary attachment content. Format is indicated by the Content-Type response header.