Parse a Document from a URL

curl -X POST 'https://api.anyformat.ai/v3/parse/from-url/' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"url": "https://example.com/invoices/april.pdf"}'

import requests

url = "https://api.anyformat.ai/v3/parse/from-url/"
headers = {"Authorization": "Bearer YOUR_API_KEY"}
body = {"url": "https://example.com/invoices/april.pdf"}

triggered = requests.post(url, headers=headers, json=body).json()
print(triggered["run_id"])

{
  "run_id": "069dcc2c-e14c-7606-8000-2ee4fb17b4fa",
  "document_packet_id": "069dcc2c-e14c-7606-8000-2ee4fb17b4e1",
  "workflow_id": "0686bb97-8c30-70f0-8000-97669e000eb8",
  "status": "queued"
}

{
  "error": "Remote fetch failed",
  "detail": "Remote server returned 404",
  "error_code": "VALIDATION_ERROR",
  "retryable": false,
  "request_id": "a1b2c3d4e5f67890abcdef1234567890"
}

POST

parse

from-url

curl -X POST 'https://api.anyformat.ai/v3/parse/from-url/' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"url": "https://example.com/invoices/april.pdf"}'

import requests

url = "https://api.anyformat.ai/v3/parse/from-url/"
headers = {"Authorization": "Bearer YOUR_API_KEY"}
body = {"url": "https://example.com/invoices/april.pdf"}

triggered = requests.post(url, headers=headers, json=body).json()
print(triggered["run_id"])

{
  "run_id": "069dcc2c-e14c-7606-8000-2ee4fb17b4fa",
  "document_packet_id": "069dcc2c-e14c-7606-8000-2ee4fb17b4e1",
  "workflow_id": "0686bb97-8c30-70f0-8000-97669e000eb8",
  "status": "queued"
}

{
  "error": "Remote fetch failed",
  "detail": "Remote server returned 404",
  "error_code": "VALIDATION_ERROR",
  "retryable": false,
  "request_id": "a1b2c3d4e5f67890abcdef1234567890"
}

Rate limit tier: submission (60 req/min) — see Rate limits. Parses one document fetched server-side from a URL with the platform’s fast lite parse — the URL analogue of POST /v3/parse/, backed by your organization’s system parse workflow (provisioned automatically on first use). Provide one HTTPS URL. The file is named by the response’s Content-Disposition, else by the URL’s path — see File names. The response is a run reference — poll GET /v3/runs/{run_id}/ until status is processed; the parsed markdown is at results.parse.markdown. A failed, non-2xx, or timed-out fetch surfaces as 422 with the failure reason in detail.

Parse is single-file per call — the results envelope carries the first file’s parse output. To import multiple URLs into one packet, use upload from URL and document-packets/run directly.

File names

A from-url file is named from the response, not from the request. The name matters twice: it carries the extension the import requires (a URL whose path is an opaque key, such as a presigned object GET, has none), and it is the name you and your users see everywhere the file is listed, so a file called by its storage key is a poor experience. Precedence:

The Content-Disposition filename on the response (RFC 6266; filename*=UTF-8''… wins over filename=, and any path is cut to its last segment).
Else the URL path’s last segment: https://example.com/invoices/april.pdf imports as april.pdf.
Else the slot mint’s extension error, as today: the import fails with 422.

The header rather than a request field, because HTTP already names a downloaded file there, every object store signs it into a presigned URL, the API stays URL-only, and the name travels with its URL instead of in a parallel list that must match urls in length and order. On S3, ResponseContentDisposition signs it in:

boto3

import boto3

s3 = boto3.client("s3")
url = s3.generate_presigned_url(
    "get_object",
    Params={
        "Bucket": "my-bucket",
        "Key": "uploads/7c1f3e9a",
        "ResponseContentDisposition": 'attachment; filename="april-invoice.pdf"',
    },
    ExpiresIn=900,
)

GCS (response-content-disposition on a V4 signed URL) and Azure (rscd on a SAS) offer the same override. Whichever name applies must end in a supported extension (.pdf, .docx, .png, …): a bare key such as uploads/7c1f3e9a names the file 7c1f3e9a, which has none, and the import fails with 422. A name that collides with a file already in the parse workflow is auto-renamed (april.pdf → april (1).pdf).

curl -X POST 'https://api.anyformat.ai/v3/parse/from-url/' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"url": "https://example.com/invoices/april.pdf"}'

import requests

url = "https://api.anyformat.ai/v3/parse/from-url/"
headers = {"Authorization": "Bearer YOUR_API_KEY"}
body = {"url": "https://example.com/invoices/april.pdf"}

triggered = requests.post(url, headers=headers, json=body).json()
print(triggered["run_id"])

{
  "run_id": "069dcc2c-e14c-7606-8000-2ee4fb17b4fa",
  "document_packet_id": "069dcc2c-e14c-7606-8000-2ee4fb17b4e1",
  "workflow_id": "0686bb97-8c30-70f0-8000-97669e000eb8",
  "status": "queued"
}

{
  "error": "Remote fetch failed",
  "detail": "Remote server returned 404",
  "error_code": "VALIDATION_ERROR",
  "retryable": false,
  "request_id": "a1b2c3d4e5f67890abcdef1234567890"
}

Authorizations

Authorization

string

header

required

API key issued from app.anyformat.ai/api-key. Send as Authorization: Bearer <key>.

Body

application/json

Body for POST /v3/parse/from-url/.

url

string

required

HTTPS URL the backend fetches server-side. The filename is derived from the URL's path.

Example:

"https://example.com/invoices/april.pdf"

Response

Successful Response

202 response for both run triggers (upload/run/ and document-packets/{id}/run/).

run_id

string

required

Unique identifier of the new run (hyphenated UUID).

Example:

"069dcc2c-e14c-7606-8000-2ee4fb17b4f9"

document_packet_id

string

required

The document packet the run executes on (hyphenated UUID).

Example:

"069dcc2c-e14c-7606-8000-2ee4fb17b4e1"

workflow_id

string

required

The workflow being run (hyphenated UUID).

Example:

"0686bb97-8c30-70f0-8000-97669e000eb8"

status

enum<string>

required

Status at acceptance time — normally queued.

Available options:

queued,

in_progress,

processed,

error,

cancelled

Example:

"queued"

Overview

Workflows

Upload

Document packets

Runs

Parse

Knowledge

Evals

SDKs and tools

API v2 (deprecated)

Parse a Document from a URL

File names

Authorizations

Body

Response

​File names

Authorizations

Body

Response

File names