# Get sitemap job status

**GET** `/v1/sitemap/{id}`

## Parameters

- `id` (path, string, required)

## Responses

### 200 — Successful response.
- `id`
- `url`
- `strategy`
- `max_depth`
- `max_urls`
- `status`
- `total_urls`
- `sources`
- `total_bytes`
- `results_url`
- `cache`
- `cache_age_s`
- `billing`
- `billing.raw_bytes`
- `billing.factors`
- `billing.factors.name`
- `billing.factors.value`
- `billing.factors.reason`
- `billing.multiplier`
- `billing.billed_bytes`
- `warnings`
- `error_code`
- `error_message`
- `compact`
- `process`
- `metadata`
- `created_at`
- `completed_at`
- `expires_at`

### 401 — Unauthorized. The request carried no valid credential, and no work was
performed. The unified `Error` envelope carries one of the codes below
in `error.code`; match on the code, never on the prose.

- `invalid_api_key` — a bearer API key was presented and rejected:
  unknown, revoked, expired or malformed. The bearer-only operations
  (`/v1/webhook-deliveries*` among them) also return it when no
  `Authorization` header is sent. `GET /v1/account` is the exception
  to "malformed": it returns `invalid_api_key` only for a key that
  starts `sk_test_` or `sk_live_` and is unknown, revoked or expired.
- `unauthorized` — the `Authorization` header is absent or malformed on
  an operation that also accepts a dashboard session (the dual-auth and
  billing operations). `GET /v1/account` also returns it, for no
  `Authorization` header and for any bearer value that does not start
  `sk_test_` or `sk_live_` (that value is checked as a dashboard
  session token).

Not retryable as-is: supply a valid API key first.
- `status`
- `error`
- `error.code`
- `error.message`
- `error.http_status`
- `error.failed_at`
- `error.details`

### 404 — Resource not found.
- `status`
- `error`
- `error.code`
- `error.message`
- `error.http_status`
- `error.failed_at`
- `error.details`

### 422 — The id path segment is not a well-formed sitemap job id (genuinely malformed — a well-formed-but-absent id returns 404, not 422; see the Inverse case in issue
- `status`
- `error`
- `error.code`
- `error.message`
- `error.http_status`
- `error.failed_at`
- `error.details`