Upload from URL
Create a document packet by importing 1–10 HTTPS URLs server-side, all-or-nothing
422 with the distinct failure reasons in detail. URLs resolving to non-globally-routable addresses (loopback, private ranges, link-local, cloud-metadata) are refused before any connection opens.
The response is final — the packet is fully imported when you receive 201. If the server-side import takes longer than the gateway’s 6-minute polling ceiling, the request fails with a 504 (retryable: true); it is safe to retry with the same request body. Trigger extraction with POST /v3/document-packets/{document_packet_id}/run/.
Authorizations
API key issued from app.anyformat.ai/api-key. Send as Authorization: Bearer <key>.
Path Parameters
Body
Body for POST /v3/workflows/{workflow_id}/upload/from-url/.
Every URL imports into a single packet atomically — any fetch or validation failure means nothing is persisted.
HTTPS URLs the backend fetches server-side (1..10). The filename is derived from each URL's path.
1 - 10 elements["https://example.com/invoices/april.pdf"]Response
Successful Response
Response for the packet-creating uploads (multipart and from-url).
Unique identifier of the newly created document packet (hyphenated UUID).
"069dcc2c-e14c-7606-8000-2ee4fb17b4e1"
The workflow the packet was created under (hyphenated UUID).
"0686bb97-8c30-70f0-8000-97669e000eb8"
Files in the packet, in the order they were provided.
