Technical support
Partnerships and sales
Service status
status.runpulse.com
Check these first
Errors and retries explains most failed requests. These problems come up often:POST /parse returns 404, or a response has a bare UUID
POST /parse returns 404, or a response has a bare UUID
The request reached API version 1. Send the
Pulse-Version: 2 header on every request, or use an SDK, which sends it for you. See Authentication.Every request returns 401
Every request returns 401
The API key is missing, mistyped, deleted or inactive. Check it under API Keys in the dashboard, or create a new one.
A result read returns 409
A result read returns 409
The job hasn’t finished yet. Poll its status until it’s
completed, then read the result. See Jobs and results.A result read returns 410, or a step refuses a parse_id
A result read returns 410, or a step refuses a parse_id
The result is gone. It expired, its job was canceled, or your organization deletes each result the first time it’s read. Run the job again. If your organization deletes results on first read, finish every step on a parse before you read the parse itself. See Jobs and results.
What to send us
Include these details, so we can find the request:- The job’s id, such as
parse-…,extract-…orbatch-…. - The response’s HTTP status and its error body.
- When it happened, with the time zone.
- The endpoint, the
configyou sent, and the file’s type and size.