> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/brand-api-reference/reference/jobs.md).

# Jobs

The `job` endpoint allows the scheduling of a job to extract data and fetch the results once complete. Jobs will protect you from hitting rate limits and will ensure a smoother data retrieval experience. This feature has been built into the [ReportExport](/brand-api-reference/reference/report-export/report-export.md) and [ClickExport](broken://pages/3846740ffc696d811e9e9d7d3bad7a10c77eef0e) where a job is scheduled automatically for you when you use this endpoint.

{% hint style="success" %}
**Note:** Read the [best practices for exporting reports and exporting clicks](/brand-api-reference/reference/report-export/best-practices-for-exporting-reports.md) to learn more.
{% endhint %}

## Job runtime

The job runtime depends on the requested data and averages around 5 seconds. The job runs as follows:

1. The job is `Scheduled`.
2. The job is `Queued` to process. Jobs with large data set requests can wait in the queue and impact the execution time.
3. The job will `Run.`
4. The job `Results` become available for download.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.impact.com/brand-api-reference/reference/jobs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.