Playground
Every API page has a form of its declared variables, seeded with their defaults, and a run button. Fastest way to answer “does this work” and “what shape is the answer” before writing any code. Runs land in the Runs tab and on the Activity page like any other.
Endpoint
Every API you build gets a function_id and one endpoint. Call it by POSTing with your Notte API key:
Your API is deployed as a Notte Function, so it is addressed by function_id. Get a key at console.notte.cc; the key decides which workspace the run is billed to.
Do not copy these by hand. Every API page and marketplace listing renders them with the real id, parameters, and defaults already filled in.
Response
Your data is in result, matching the schema on the API’s page. The envelope around it identifies the run and, when the API opened a browser, the session it used.
Add "stream": true to the body to get SSE log lines as the run happens instead of one JSON body at the end.
Variables
variables is keyed by the API’s declared variable names. Omitted values fall back to their defaults. Types are the API’s own: a numeric parameter takes a number, not a string.
When a run fails
A run that raises still returns 200, with the traceback in result. Inspect the payload rather than the HTTP code: an input mistake and a site change look different in the traceback, and a site change is what wakes self-healing.
