Skip to main content

Troubleshooting

  • 401 · Missing, expired, or revoked credential. Check the key or reconnect.
  • 403 · Check the requested scope, account access, and provider permissions. NATIVE_REQUEST_REQUIRED means a Cookie or Origin header was sent.
  • 404 / 410 · The record is unavailable, belongs to another account, or has been deleted. Do not recreate a deleted note by replaying an old request.
  • 409 · The saved version changed, an operation key was reused with different input, or a previous result is still unknown. Read the latest state before retrying.
  • 422 · The request body or query was rejected. error stays INVALID_REQUEST (or a more specific code) and issues lists each rejected field as { path, code }, for example REQUIRED, UNKNOWN_FIELD, INVALID_TYPE, INVALID_FORMAT or TOO_LONG. Submitted values are never echoed. Fix the named fields and send the request again. Context writes keep their own error message without issues.
  • 429 · A request or usage limit was reached. Respect Retry-After when present and check your plan’s usage.
  • 5xx / connection lost · Check whether the original operation completed before retrying any write or publishing request.

Need a hand?

Send the endpoint, HTTP status, error code, and approximate request time. Never send an API key, authorization code, token, or private note content.

Get help