Sign inStart free

Developer documentation

The not24get public API is a JSON HTTP API. This section covers everything you need to ship a reliable integration: authentication, rate limits, errors, pagination, and per-endpoint reference with request/response schemas and a browser Try-it runner.

Start here if you are wiring CI, a backend service, or a CLI to create and list bookmarks. Product how-tos for humans live in the User manual; this section assumes you already have a workspace and can create an API key.

Get oriented

  • Authentication — JWT vs API keys, headers, scoping by workspace.
  • Rate limits — limits per key, per IP, and per tenant; backoff guidance.
  • Errors — the standard error envelope and how to use correlation_id.
  • Pagination — list endpoints, cursors, and page sizes.
  • Tenant usage — GET /billing/usage returns usage meters and effective limits for the tenant implied by your JWT or API key (same tenant-admin access as the product billing area). See the usage group in the API reference.

Resource reference

Pick a resource on the left to see every operation, its parameters, request/response schemas, code samples, and a working Try-it form. Common entry points:

Conventions

  • All requests and responses are JSON unless explicitly noted.
  • All times are RFC 3339 / ISO 8601 strings in UTC.
  • IDs are opaque strings; do not parse them.
  • The base URL is https://api.not24get.me. Treat it as configurable in your client.

Prerequisites for first call

  1. Create a workspace API key in the product (Create an API key).
  2. Store it as an environment variable (for example N24M_API_KEY).
  3. Send Authorization: Bearer … on every authenticated request.
  4. For workspace-scoped routes, also send X-Workspace-ID when required (Authentication).

Troubleshooting integrations

  • 401 — missing or revoked credentials; recreate the key and verify the Bearer header.
  • 403 — valid token, insufficient permission; check tenant role and workspace membership.
  • 429 — honor Retry-After and read Rate limits.
  • Unexpected empty lists — confirm workspace ID and pagination cursors (Pagination).
  • Need a human-readable walkthrough — Use an API key.