> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runpulse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Support

> How to reach Pulse, what to check first, and what to send with a question.

Email Pulse with technical questions, bugs and feature requests, or about partnerships and enterprise plans. If requests start failing across the board, check the status page first.

> [card] [Technical support](mailto:support@trypulse.ai)
>
> [support@trypulse.ai](mailto:support@trypulse.ai)

> [card] [Partnerships and sales](mailto:hello@trypulse.ai)
>
> [hello@trypulse.ai](mailto:hello@trypulse.ai)

> [card] [Service status](https://status.runpulse.com)
>
> status.runpulse.com

## Check these first

[Errors and retries](https://docs.runpulse.com/v2/errors.md) explains most failed requests. These problems come up often:

> [accordion] 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](https://docs.runpulse.com/v2/authentication.md#without-pulse-version).

> [accordion] Every request returns 401
>
> The API key is missing, mistyped, deleted or inactive. Check it under **API Keys** in the [dashboard](https://platform.runpulse.com), or create a new one.

> [accordion] 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](https://docs.runpulse.com/v2/jobs.md).

> [accordion] 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](https://docs.runpulse.com/v2/jobs.md#retention).

## What to send us

Include these details, so we can find the request:

* The job's id, such as `parse-…`, `extract-…` or `batch-…`.
* The response's HTTP status and its error body.
* When it happened, with the time zone.
* The endpoint, the `config` you sent, and the file's type and size.

> [!WARNING]
>
> Never send an API key or a webhook secret. Remove them from any code, config or log you share.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.