Get data using alternative methods

Webhooks are the recommended way to receive your parsed data in real time. See Webhooks for setup and best practices.

If webhooks aren’t an option (e.g., no public endpoint, restricted network, or policy constraints), use one of the alternatives below to fetch or route your data.

Alternatives to webhooks to get your parsed data

Automation platforms: Send data to third-party apps (Zapier, Make, n8n, Power Automate, etc.).

Polling /document/{id}: Manually fetch a single document’s parsed result

Download URLs: Pull mailbox-level CSV/JSON/Excel exports via stable URLs.

Processing in Parseur is asynchronous. A successful upload means the document was received; extraction happens afterward.

1) Automation platforms

If you want to send data to another application, there’s a good chance it’s supported by an automation platform.

Parseur has native connectors for popular tools like Zapier, Make, n8n, Power Automate, and more.

You can set up a webhook to your favorite app in just a few clicks, with no coding required.

Learn more:

Read our Guides & how‑tos

Browse featured integrations

2) Polling on `/document/{id}`

Use this only if you cannot set up webhooks. Poll the document endpoint until processing is done, then parse the result.

Polling increases load and latency. Prefer webhooks when possible and keep requests within your plan’s Rate limits.

Get a document

Example response (trimmed)

{
  "id": "123456789",
  "status": "PARSEDOK",
  "result": "{\"order_id\":\"12345\",\"total\":199.99,\"items\":[{\"sku\":\"ABC\",\"qty\":2}]}"
}

See Get a document for the full response schema.

Parse the result JSON string

With jq fromjson (shell)

With JavaScript

With Python

3) Download URLs

Download URLs let you pull mailbox‑level data exports without calling the API for each document.

Download URLs don’t change over time.

They are publicly accessible; keep the URLs secret (treat like credentials).

Standard download URLs

A GET /parser/{id} returns links for CSV, JSON, and Excel:

csv_download

json_download

xls_download

See Endpoints → Mailbox (Parser) → Get a mailbox for the full response schema.

You can then fetch, for example, the JSON export directly:

Custom download URLs

If you configured custom downloads in the mailbox, list them with GET /parser/{id}/export_config

See Endpoints → Mailbox (Parser) → List custom downloads for the full response schema.

Download URL query parameters

Both standard and custom download URLs support passing query parameters to filter the data.

last_document_only=true: return only the data from the most recent document.

date=YYYY or date=YYYY-MM or date=YYYY-MM-DD: return data for documents received in that UTC range.

Examples:

For more details, check out the Manually download extracted data

Quick reference

Prefer Webhooks for real-time, push-based delivery.

Use Automation platforms for plug-and-play no-code app integrations.

Use polling on /document/{id} only if you can’t use webhooks; parse result with JSON.parse, json.loads, jq fromjson or equivalent in your favorite language.

Use Download URLs for mailbox-level CSV/JSON/Excel pulls; keep URLs secret.

Stay within Rate limits.

Alternatives to webhooks to get your parsed data#

1) Automation platforms#

2) Polling on /document/{id}#

Get a document#

Example response (trimmed)#

Parse the result JSON string#

With jq fromjson (shell)#

With JavaScript#

With Python#

3) Download URLs#

Standard download URLs#

Custom download URLs#

Download URL query parameters#

Quick reference#

Alternatives to webhooks to get your parsed data

1) Automation platforms

2) Polling on `/document/{id}`

Get a document

Example response (trimmed)

Parse the result JSON string

With jq fromjson (shell)

With JavaScript

With Python

3) Download URLs

Standard download URLs

Custom download URLs

Download URL query parameters

Quick reference