HTTP 404Resource not found

resource_not_found

No resource with that id is visible to this key's organization. Ids are org-scoped: another workspace's post id answers 404, not 403 — existence is never leaked across organizations.

This page is where the problem type URI https://usepostify.com/docs/api/problems/resource-not-found resolves.

Common causes

  • The id is from a different workspace than the key's.
  • The resource was deleted.
  • The id was mangled in transit (truncation, URL-encoding issues).

How to fix

  • List the collection (e.g. GET /v1/posts) and confirm the id exists for this workspace.
  • Check which workspace the key belongs to in Settings → API keys.

Example response

404 · application/problem+json
{
  "type": "https://usepostify.com/docs/api/problems/resource-not-found",
  "title": "Resource not found",
  "status": 404,
  "code": "resource_not_found",
  "detail": "No post with this id exists in this workspace.",
  "request_id": "req_6f1f8a2b40d34cd2a6f1e2c9b8d7a601"
}

Related