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

# Output Response - Job Posting Search API

# Output Response

## Response Data Structure

Here is an example response from the Job Posting Search API:

```json
{
    "status": 200,
    "data": [
        {
          "id": "mCxejm1sT+Q",
          "first_seen": "2025-02-27",
          "last_verified": "2025-02-27",
          ... // Rest of the details for this Job Posting record
        },
        ... // Rest of the Job Posting records in the response
    ],
    "total": 6,
    "scroll_token": "13.312621$543927",
    "dataset_version": "34.0"
}
```

<br />

## Response Fields

***

<br />

### `data.*`

| Type             | Description                                                                                                                                                                                                                                |
| :--------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Array (Object)` | The job posting record objects that match the input query in the format described in our [Job Posting Dataset](https://docs.peopledatalabs.com/docs/job-posting-data-overview). Records are sorted by most recent (based on `first_seen`). |

The `data` list is made up of objects that contain the full PDL record for each job posting that matches the API request. Any fields within these records that we do not have data for will have a `null` value.

See the [Example Job Posting Record](https://docs.peopledatalabs.com/docs/example-job-posting-record) for an example of a full job posting record that would be contained in the `data` array.

<Callout icon="📘" theme="info">
  **Sorting**

  Job posting records are sorted in the `data` array based the most recent records first (using the `first_seen` field of each record.
</Callout>

<br />

<br />

***

<br />

### `status`

| Type      | Description                          |
| :-------- | :----------------------------------- |
| `Integer` | The [API response code](https://docs.peopledatalabs.com/docs/errors). |

***

<br />

### `total`

| Type      | Description                                               |
| :-------- | :-------------------------------------------------------- |
| `Integer` | The total number of records that matched the input query. |

***

<br />

### `scroll_token`

| Type     | Description                                                               |
| :------- | :------------------------------------------------------------------------ |
| `String` | The scroll token to use to fetch the next batch of results for the query. |

If your query matches more records than are returned in the current response, use the `scroll_token` value in your next request to retrieve the next batch.

Example:

```json
{
  "company_name": "openai",
  "title_role": "engineering",
  "size": 3,
  "scroll_token": "PASTE_SCROLL_TOKEN_HERE",
  "api_key": "YOUR_API_KEY"
}
```

Keep sending the same query with the newest `scroll_token` until you have the records you need or the pagination is complete.

For a complete working example, see [Examples](https://docs.peopledatalabs.com/docs/examples-job-posting-api).

***

<br />

### `dataset_version`

| Type     | Description                                                           |
| :------- | :-------------------------------------------------------------------- |
| `String` | The current release version of the data included in the API response. |

This field indicates which underlying Job Posting dataset release was used to generate the response.