Public API
Coming Soon

Scoped permissions

Reads need nothing: content:read and pricing:read are granted to every caller, because the same information is already on the website. Writes need a token from the OAuth 2.0 client credentials endpoint, and a client is only ever issued the scopes it was registered for, so an agent holds exactly the access it needs.

curl -u $CLIENT_ID:$CLIENT_SECRET \
  -d grant_type=client_credentials \
  -d scope=newsletter:write \
  https://www.1capture.io/api/v1/oauth/token

Credentials are issued on request: email contact@1capture.io.

Errors are always JSON

Nothing under /api returns an HTML error page. Every failure carries a stable code, a message, and a resolution hint that says what to do next.

{
  "error": {
    "code": "insufficient_scope",
    "message": "The access token is missing the newsletter:write scope.",
    "resolution": "Request a new token that includes scope=newsletter:write.",
    "documentation_url": "https://www.1capture.io/docs/api",
    "request_id": "6f1b4689-95df-cbcab835e840"
  },
  "status": 403
}