404

Do not retry

Not found — Either the path is not an endpoint (`not_found`), or you tried to block a company your account cannot see (`source_not_found`). A missing record on a read is a `200`, not this.

Response body

{ "error": { "code": "not_found" | "source_not_found", … } }

Should you retry?

No — the same request will fail the same way. Fix it first.

What it means

Switch on error.code — there are two cases. not_found is about routing: the URL you called is not a real endpoint at all. source_not_found comes only from POST /v4/sources/blocked/<source_id>: the id is not a company your account can see, and nothing was stored; error.details.source_id echoes it. Neither means a record is missing from a read — a job or company that does not exist, or is out of your scope, is a 200 with an empty result — see not-found semantics.

Common causes

A typo in the path.
A v3 path called against the v4 host, or vice versa.
A path built by hand that does not match any documented route.
`source_not_found` — blocking with a company URL, a mistyped id, or a lowercased one (ids are case-sensitive).

How to fix it

Check the path against the V4 API reference — a bug to fix, not to retry. For source_not_found, take the id from a company record's id.

Endpoints that return this

Read from the OpenAPI specification, so this list cannot claim an endpoint returns a status the contract does not list.

Method	Endpoint	What it does
POST	/v4/sources/blocked/{source_id}	Block a company

404