Skip to main content
Invoice Supporting Documents API

Authentication

All requests require an API key in the request headers. Headers:

Request

Content-Type: application/json

Path Parameters

Code Examples

Success Response

HTTP Status: 200 OK Response Fields:

Response Example

Empty Results

When the invoice has no supporting documents attached, an empty array is returned:

Error Responses

Missing Invoice ID

HTTP Status: 400 Bad Request

Invoice Not Found

HTTP Status: 404 Not Found

Access Denied

HTTP Status: 403 Forbidden
Returned when the caller is not an admin / bookkeeper, did not create the invoice, and is not the owner of its vendor.

Authentication Errors

HTTP Status: 401 Unauthorized

Permission Errors

HTTP Status: 403 Forbidden

Internal Error

HTTP Status: 500 Internal Server Error

Best Practices

  • The downloadUrl points at the Download File API — call it with the same Authorization header to retrieve the file bytes
  • Use the Invoice Supporting Document Upload API to add more files against the same invoice
  • The extension field is uppercased and falls back to UNK if the underlying MIME type is missing