Sign inStart free

Use an API key

After you have created an API key, you can call any public endpoint by sending the key in the Authorization header.

This page walks through the minimum successful request, a workspace-scoped write, and how to try the same calls from the docs Try it panel. Keep keys out of shell history when you can: prefer environment variables or a secrets manager over pasting into scripts that you commit.

Prerequisites

  • A workspace API key stored as N24M_API_KEY (or equivalent) in your environment.
  • Network access to https://api.not24get.me.
  • For workspace-scoped writes, the workspace ID from Workspace settings → General.
  • Familiarity with Authentication and Errors.

The minimum request

Set N24M_API_KEY in your shell to the key you copied when you created it.

curl --request GET \
  --url 'https://api.not24get.me/api/v1/me' \
  --header "Authorization: Bearer ${N24M_API_KEY}"

A successful response returns your account profile as JSON. If the key is invalid or revoked, the response is 401 with error.code = "unauthorized".

Workspace-scoped requests

Most operations work inside a workspace. For those, add the X-Workspace-ID header:

curl --request POST \
  --url 'https://api.not24get.me/api/v1/bookmarks' \
  --header "Authorization: Bearer ${N24M_API_KEY}" \
  --header 'X-Workspace-ID: YOUR_WORKSPACE_ID' \
  --header 'Content-Type: application/json' \
  --data '{
    "url": "https://example.com",
    "title": "Example"
  }'

You can find a workspace's ID under Workspace settings → General.

Try it from the browser

Every endpoint in the API reference has a Try it panel. Set your API key in the header (top right of the docs) and the panel will issue real requests against your account.

Troubleshooting

  • 401 unauthorized — key missing, mistyped, or revoked. Recreate the key and confirm the Bearer prefix has a single space before the secret.
  • 403 forbidden — the key is valid but lacks permission for that resource. Check tenant role and workspace membership.
  • validation_error on workspace routes — supply X-Workspace-ID, or ensure the key has a default workspace. See Authentication.
  • 429 rate_limited — slow down and honor Retry-After. Details in Rate limits.
  • CORS errors from a browser app — call the API from your backend, or use the docs Try-it panel which is allow-listed for docs origins.