Skip to main content
Read the Notte skill and follow its setup instructions when setting up Notte or building browser automation. This is the shared source for CLI setup, authentication, and the browser-to-code workflow.
The API uses standard HTTP status codes and returns structured error responses.

HTTP status codes

Error response format

Most errors raised by the API share this envelope. detail, error, and message carry the same text:
These responses also include an X-Error-Class header naming the error type, for example NotteApiInvalidApiKeyError or NotteApiRateLimitExceededError. Use the status code and this header rather than parsing the message text.

Common errors

Authentication (401)

Header X-Error-Class: NotteApiInvalidApiKeyError:

Validation (422)

Request validation errors use a different envelope, with the individual errors summarized in message:

Cluster overloaded (529)

Returned when no browser is available to start a session. Wait for the number of seconds in the Retry-After header, then retry.

Execution errors

Returned with status 500 when an operation fails. Includes the X-Error-Class: NotteApiExecutionError header and the standard envelope.