List this directory's jobs
Requires read:drafts or write. A job row carries inputJson and errorJson, which describe work on unpublished content, so this is gated with the same pair as the dead-link report — a monitoring cron should not need a key that can delete every listing just to poll progress.
Jobs enqueued through POST .../jobs appear here. Nothing else does. JobsService is the only writer of a job row in the platform, and the sweep routes — POST .../screenshots, POST .../research, POST .../site-probes/sweep, POST .../enrich — enqueue into the queue directly and create no row. So if you start a sweep and poll here you will see an empty list, and the sweep is fine. Use each sweep's own coverage endpoint until those routes are wired to create a job row; this note goes away when they are.
Newest first, with id as a tiebreak: one import fans out hundreds of jobs inside the same millisecond, so without the second sort key two pages of the same list can repeat and skip rows.
Request
- Base URL: https://api.epicdirectories.com
- URL: https://api.epicdirectories.com/public/v1/directories/{directory}/jobs
- Auth: API key in header x-api-key
Path parameters
Query parameters
pending, queued, processing, completed, failed or cancelled.
Default 50, max 200.
Headers
Optional. Send a unique key per logical operation to make retries safe. 1-256 characters, and only letters, digits, - and _ — colons and other separators are rejected with 400. A retry with the same key replays the original response (status + body) instead of re-executing. Cached for 24h. Reusing a key with a different request body returns 409 — note that a timestamp in the body (e.g. fetchedAt) turns an otherwise-stable key into a permanent 409, so either omit it (snapshots default it server-side) or fold a payload digest into the key. Skipped on 5xx responses (transient errors should be retried fresh).
API Key for authentication
Response
Jobs, newest first
Changes
No recorded changes to this operation across all 1 revision of this API.