> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developer.jelliu.co/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developer.jelliu.co/_mcp/server.

# List export jobs

GET https://api.jelliu.co/api/exports

Returns the workspace's export jobs of every type and status, newest first. Jobs created by any
member are included, even `audit_log` and `agent_actions` jobs: their metadata is listed here,
but reading or downloading one individually still needs the admin role.

Uses offset pagination with `limit` and `offset`. The response has no total and no cursor: keep
requesting pages until one comes back with fewer than `limit` jobs. See [Pagination](/pagination).

**Consistency.** Each page is cached for 30 seconds. Creating or deleting a job clears the cache,
but a worker finishing a job does not, so a job can show as `pending` or `processing` here for up
to 30 seconds after it completed. Poll `GET /api/exports/{id}` for status; it is not cached.

**Idempotency.** A read with no side effects. Safe to retry.

**Access**

* **Required scope:** `read` or `write`. Any workspace role can call it.
* **Rate limit:** General API — 120 requests/min per workspace on Starter or with no active plan, 200 on Growth, 300 on Business, 600 on Enterprise. See [Rate limits](/rate-limits).
* **Plan:** Available on every plan.

Reference: https://developer.jelliu.co/api-reference/exports/get-exports

## Authentication

- `Authorization` header (bearer token, required) — Workspace API key: `jl_` followed by 64 lowercase hex characters, created by the workspace owner in the dashboard (**Settings → API Keys**) and sent as `Authorization: Bearer jl_...`. The plaintext is shown once, at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys. | Scope | GET / HEAD | POST / PUT / PATCH / DELETE | Admin-only routes | | --- | --- | --- | --- | | `read` | Yes | No | No | | `write` | Yes | Yes | No | | `full` | Yes | Yes | Yes | Operations restricted to admins or owners reject keys without the `full` scope with `403`, and say so in their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret — that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds. See [Authentication](/authentication).

## Request

### Query parameters

- `limit` (integer, optional, default: 50) — Page size. An integer from 1 to 100; anything else is rejected with `400`, not clamped.
- `offset` (integer, optional, default: 0) — Number of jobs to skip. An integer from 0 to 100000; anything else is rejected with `400`.

## Response

### 200

Export jobs, newest first.

- `data` (list of object, required) — Jobs ordered by `created_at` descending.
  - `id` (string, optional) — Job id. Use it with `GET /api/exports/{id}` and `/download`.
  - `tenant_id` (string, optional) — The workspace that owns the job.
  - `user_id` (string, optional) — Who requested it. A dashboard user id, or `apikey:<keyId>` for API-key requests. This user gets the in-app notification.
  - `type` (enum, optional) — Data set exported. `calls`, `contacts`, `conversations`, `analytics` (daily aggregates per campaign), `agent_actions` and `audit_log` (both owner/admin only).
    - Allowed values: `calls`, `contacts`, `conversations`, `analytics`, `agent_actions`, `audit_log`
  - `format` (enum, optional) — File format. `csv`, `json` (one array) or `jsonl` (one object per line).
    - Allowed values: `csv`, `json`, `jsonl`
  - `status` (enum, optional) — `pending`: queued. `processing`: a worker is building the file. `completed`: ready to download until `expires_at`. `failed`: see `error`. A failed job is retried once about 10 s later, so it can go back to `processing`.
    - Allowed values: `pending`, `processing`, `completed`, `failed`
  - `filters` (map from string to any, optional) — The filters sent on creation, as stored (`{}` when none).
  - `row_count` (integer, optional, nullable) — Rows written to the file (at most 100000). Null until completed.
  - `file_size_bytes` (integer, optional, nullable) — File size in bytes. Null until completed.
  - `file_url` (string, optional, nullable) — Internal storage reference, not a downloadable URL. Always download through `GET /api/exports/{id}/download`. Cleared when the cleanup sweep removes the file.
  - `error` (string, optional, nullable) — Failure reason on `failed` jobs. On a `completed` job, `Results truncated to 100000 rows` when the result was cut short. Otherwise null.
  - `started_at` (datetime, optional, nullable) — When a worker started processing (updated on the retry).
  - `completed_at` (datetime, optional, nullable) — When the job finished, successfully or not.
  - `expires_at` (datetime, optional, nullable) — Set on completion, 72 hours later. After it, the download answers `410`.
  - `created_at` (datetime, optional) — When the job was created.

## Errors

### 400 Bad Request Error

`limit` or `offset` is out of range or not an integer.

- `error` (object, required) — The error object. Always has `code` and `message`.
  - `code` (string, required) — Stable machine-readable error code (for example `VALIDATION_FAILED`, `UNAUTHORIZED`, `FORBIDDEN`, `NOT_FOUND`, `BILLING_ERROR`, `COMPLIANCE_BLOCKED`, `RATE_LIMIT_EXCEEDED`, `INTERNAL_ERROR`). Switch on this, not on `message`. See [Errors](/errors).
  - `message` (string, required) — Human-readable explanation. English or Spanish depending on the route; may change without notice.
  - `details` (object or list of object, optional) — Present on `VALIDATION_FAILED` only. Its shape depends on how the route validates: * a field map, either Zod's `flatten()` output (`{ "formErrors": [], "fieldErrors": { "name": ["..."] } }`) or just its `fieldErrors` part (`{ "name": ["..."] }`); * an issue list, where each issue has at least `path`, `message` and `code`. `path` is a dot-separated string on routes that let the schema throw, and an array of keys on routes that forward Zod's raw issues (those also carry Zod's extra issue fields).
    - Field map
      - `formErrors` (list of string, optional)
      - `fieldErrors` (map from string to list of string, optional)
  - `metadata` (map from string to any, optional) — Structured detail exposed for a small allowlist of codes only — for example `BILLING_ERROR` carries `limit`, `current` and `tier` (resource caps) or `tier` and `feature` (feature gates).

### 401 Unauthorized Error

No usable credential. Either the `Authorization` header is missing or is not a well-formed `Bearer jl_…` key, or the key is unknown, revoked or expired. Do not retry with the same key. See [Authentication](/authentication#401-unauthorized).

- `error` (object, required) — The error object. Always has `code` and `message`.
  - `code` (string, required) — Stable machine-readable error code (for example `VALIDATION_FAILED`, `UNAUTHORIZED`, `FORBIDDEN`, `NOT_FOUND`, `BILLING_ERROR`, `COMPLIANCE_BLOCKED`, `RATE_LIMIT_EXCEEDED`, `INTERNAL_ERROR`). Switch on this, not on `message`. See [Errors](/errors).
  - `message` (string, required) — Human-readable explanation. English or Spanish depending on the route; may change without notice.
  - `details` (object or list of object, optional) — Present on `VALIDATION_FAILED` only. Its shape depends on how the route validates: * a field map, either Zod's `flatten()` output (`{ "formErrors": [], "fieldErrors": { "name": ["..."] } }`) or just its `fieldErrors` part (`{ "name": ["..."] }`); * an issue list, where each issue has at least `path`, `message` and `code`. `path` is a dot-separated string on routes that let the schema throw, and an array of keys on routes that forward Zod's raw issues (those also carry Zod's extra issue fields).
    - Field map
      - `formErrors` (list of string, optional)
      - `fieldErrors` (map from string to list of string, optional)
  - `metadata` (map from string to any, optional) — Structured detail exposed for a small allowlist of codes only — for example `BILLING_ERROR` carries `limit`, `current` and `tier` (resource caps) or `tier` and `feature` (feature gates).

### 403 Forbidden Error

Authenticated, but not allowed: the key's scope does not cover the method, the route is restricted to workspace admins/owners and the key is not `full`, or the workspace is suspended (`TENANT_SUSPENDED`). See [Authentication](/authentication#scopes).

- `error` (object, required) — The error object. Always has `code` and `message`.
  - `code` (string, required) — Stable machine-readable error code (for example `VALIDATION_FAILED`, `UNAUTHORIZED`, `FORBIDDEN`, `NOT_FOUND`, `BILLING_ERROR`, `COMPLIANCE_BLOCKED`, `RATE_LIMIT_EXCEEDED`, `INTERNAL_ERROR`). Switch on this, not on `message`. See [Errors](/errors).
  - `message` (string, required) — Human-readable explanation. English or Spanish depending on the route; may change without notice.
  - `details` (object or list of object, optional) — Present on `VALIDATION_FAILED` only. Its shape depends on how the route validates: * a field map, either Zod's `flatten()` output (`{ "formErrors": [], "fieldErrors": { "name": ["..."] } }`) or just its `fieldErrors` part (`{ "name": ["..."] }`); * an issue list, where each issue has at least `path`, `message` and `code`. `path` is a dot-separated string on routes that let the schema throw, and an array of keys on routes that forward Zod's raw issues (those also carry Zod's extra issue fields).
    - Field map
      - `formErrors` (list of string, optional)
      - `fieldErrors` (map from string to list of string, optional)
  - `metadata` (map from string to any, optional) — Structured detail exposed for a small allowlist of codes only — for example `BILLING_ERROR` carries `limit`, `current` and `tier` (resource caps) or `tier` and `feature` (feature gates).

### 429 Too Many Requests Error

Rate limit exceeded for the current 60-second window (`RATE_LIMIT_EXCEEDED`). Wait `Retry-After` seconds, then retry. The `message` differs per limiter; the code does not. See [Rate limits](/rate-limits).

- `error` (object, required) — The error object. Always has `code` and `message`.
  - `code` (string, required) — Stable machine-readable error code (for example `VALIDATION_FAILED`, `UNAUTHORIZED`, `FORBIDDEN`, `NOT_FOUND`, `BILLING_ERROR`, `COMPLIANCE_BLOCKED`, `RATE_LIMIT_EXCEEDED`, `INTERNAL_ERROR`). Switch on this, not on `message`. See [Errors](/errors).
  - `message` (string, required) — Human-readable explanation. English or Spanish depending on the route; may change without notice.
  - `details` (object or list of object, optional) — Present on `VALIDATION_FAILED` only. Its shape depends on how the route validates: * a field map, either Zod's `flatten()` output (`{ "formErrors": [], "fieldErrors": { "name": ["..."] } }`) or just its `fieldErrors` part (`{ "name": ["..."] }`); * an issue list, where each issue has at least `path`, `message` and `code`. `path` is a dot-separated string on routes that let the schema throw, and an array of keys on routes that forward Zod's raw issues (those also carry Zod's extra issue fields).
    - Field map
      - `formErrors` (list of string, optional)
      - `fieldErrors` (map from string to list of string, optional)
  - `metadata` (map from string to any, optional) — Structured detail exposed for a small allowlist of codes only — for example `BILLING_ERROR` carries `limit`, `current` and `tier` (resource caps) or `tier` and `feature` (feature gates).

## Examples

**Response**

```json
{
  "data": [
    {
      "id": "8e2d4f6a-1c3b-4d5e-9f7a-2b4c6d8e0f1a",
      "tenant_id": "7a1b2c3d-4e5f-4a6b-8c7d-9e0f1a2b3c4d",
      "user_id": "user_2kLmNoPqRsTuVwXyZ",
      "type": "contacts",
      "format": "jsonl",
      "status": "processing",
      "filters": {
        "campaign_id": "0b3e7c52-8d4f-4a11-b2c9-5e6f7a8b9c0d"
      },
      "row_count": null,
      "file_size_bytes": null,
      "file_url": null,
      "error": null,
      "started_at": "2026-09-14T16:02:03.114Z",
      "completed_at": null,
      "expires_at": null,
      "created_at": "2026-09-14T16:02:01.902Z"
    },
    {
      "id": "5e4d3c2b-1a09-4f8e-9d7c-6b5a4f3e2d1c",
      "tenant_id": "7a1b2c3d-4e5f-4a6b-8c7d-9e0f1a2b3c4d",
      "user_id": "apikey:4f1e2d3c-5b6a-4978-8a9b-0c1d2e3f4a5b",
      "type": "calls",
      "format": "csv",
      "status": "completed",
      "filters": {
        "date_from": "2026-09-01T00:00:00Z",
        "date_to": "2026-09-14T23:59:59Z"
      },
      "row_count": 1824,
      "file_size_bytes": 412733,
      "file_url": "/tmp/jellow-exports/7a1b2c3d-4e5f-4a6b-8c7d-9e0f1a2b3c4d/calls_5e4d3c2b-1a09-4f8e-9d7c-6b5a4f3e2d1c.csv",
      "error": null,
      "started_at": "2026-09-14T15:10:02.410Z",
      "completed_at": "2026-09-14T15:10:09.877Z",
      "expires_at": "2026-09-17T15:10:09.877Z",
      "created_at": "2026-09-14T15:10:01.995Z"
    }
  ]
}
```

**SDK Code**

```python Exports_getExports_example
import requests

url = "https://api.jelliu.co/api/exports"

querystring = {"limit":"20","offset":"20"}

headers = {"Authorization": "Bearer <token>"}

response = requests.get(url, headers=headers, params=querystring)

print(response.json())
```

```javascript Exports_getExports_example
const url = 'https://api.jelliu.co/api/exports?limit=20&offset=20';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}
```

```go Exports_getExports_example
package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.jelliu.co/api/exports?limit=20&offset=20"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(res)
	fmt.Println(string(body))

}
```

```ruby Exports_getExports_example
require 'uri'
require 'net/http'

url = URI("https://api.jelliu.co/api/exports?limit=20&offset=20")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Get.new(url)
request["Authorization"] = 'Bearer <token>'

response = http.request(request)
puts response.read_body
```

```java Exports_getExports_example
import com.mashape.unirest.http.HttpResponse;
import com.mashape.unirest.http.Unirest;

HttpResponse<String> response = Unirest.get("https://api.jelliu.co/api/exports?limit=20&offset=20")
  .header("Authorization", "Bearer <token>")
  .asString();
```

```php Exports_getExports_example
<?php
require_once('vendor/autoload.php');

$client = new \GuzzleHttp\Client();

$response = $client->request('GET', 'https://api.jelliu.co/api/exports?limit=20&offset=20', [
  'headers' => [
    'Authorization' => 'Bearer <token>',
  ],
]);

echo $response->getBody();
```

```csharp Exports_getExports_example
using RestSharp;

var client = new RestClient("https://api.jelliu.co/api/exports?limit=20&offset=20");
var request = new RestRequest(Method.GET);
request.AddHeader("Authorization", "Bearer <token>");
IRestResponse response = client.Execute(request);
```

```swift Exports_getExports_example
import Foundation

let headers = ["Authorization": "Bearer <token>"]

let request = NSMutableURLRequest(url: NSURL(string: "https://api.jelliu.co/api/exports?limit=20&offset=20")! as URL,
                                        cachePolicy: .useProtocolCachePolicy,
                                    timeoutInterval: 10.0)
request.httpMethod = "GET"
request.allHTTPHeaderFields = headers

let session = URLSession.shared
let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
  if (error != nil) {
    print(error as Any)
  } else {
    let httpResponse = response as? HTTPURLResponse
    print(httpResponse)
  }
})

dataTask.resume()
```