NL Official DocumentsOrderCopy PageDownload a document from an orderget https://api.company.info/nl/organizations/official-documents/v1/orders/{order_id}/documentDownload a document from an orderPath Paramsorder_idstringrequiredHeadersacceptstringenumDefaults to application/jsonGenerated from available response content typesapplication/jsonapplication/pdfapplication/vnd.api+jsonapplication/ziptext/htmlAllowed:application/jsonapplication/pdfapplication/vnd.api+jsonapplication/ziptext/htmlResponses 200Returns PDF/HTML/JSON/ZIP 400The request is malformed or semantically invalid. This covers three distinct sub-cases that look identical on the wire: Local validation (detail prefixed with ordering: or documents: or pagination:) — the request body / query string does not meet the schema (e.g. an organizationID that is not 8 digits, a missing required filter). Fix by correcting the request. Business-rule validation (detail: the document type is not supported for this company) — the discovery endpoint does not list this combination for this organization. Fix by calling GET /v1/ first and ordering from the result. Upstream rejection — company not found, more than one company found, or invalid document type. Fix depends on which: client input errors (company not found, invalid document type) should be corrected by the caller; permission errors require Company.info support. 401Authentication is missing or invalid. 404The addressed resource (order_id or document_id) does not exist, or does exist but belongs to a different customer. Source: server (lookup). Retryable: no. Caller action: verify the ID and confirm the correct API key / customer is being used. 406The format requested via the Accept header is not available for this document. The mimeTypes array on the order / document response lists the formats that can actually be downloaded — pick one of those values. 423The resource is in a transient state and cannot yet satisfy the request. Common cases: Downloading an order whose status is not yet done. Retrying the convert activity before the order has completed ordering. Retrying the order activity on an order that has not timed out / failed. 500An unexpected failure in Service itself. The detail is intentionally generic (an error occurred on <action>) to avoid leaking internal state — the information needed to diagnose a specific occurrence is in the server-side logs keyed by X-Correlation-Id. Source: server / platform. Retryable: yes for the generic an error occurred on … variants, with exponential back-off (start at ~1 s). If a transient error persists for more than a few minutes, contact support with the X-Correlation-Id.Updated 4 months ago Retry a failed order activityDocumentDid this page help you?YesNo