Discard a setup that has not reached its first run
const url = 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/setup/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/discard';const options = { method: 'POST', headers: {'X-Katara-CSRF': '1', Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/setup/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/discard \ --header 'Authorization: Bearer <token>' \ --header 'X-Katara-CSRF: 1'Only the person who started a setup can discard it, and only before its first run is admitted. Its payer consent is revoked and its budget closed, which returns the credit it held; the agent and documents it made stay. Discarding again changes nothing.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Header Parameters
Section titled “Header Parameters”Browser cookie mutations require value 1 and an allowed Origin. Session bearer clients may omit this header.
Required for cookie-authenticated changes. Use the UUID of the account that loaded the application. A different current cookie account returns account_changed before the handler runs. Session bearer and API key clients do not require this header.
Responses
Section titled “Responses”Successful request
How far a setup has come and the request it was started with. A setup is done once its first run is admitted and discarded once its person gives it up; while running, starting again with the same request continues it.
object
The starter agent to set up. A blank agent also carries the instructions and first task the person wrote; the other starters carry neither.
object
One step of a setup and whether it has finished.
object
Example
{ "starter": "assistant", "request": { "starter": "assistant" }, "state": "running", "steps": [ { "name": "agent" } ]}Conflict: the setup reached its first run; account_changed: reload and review with the signed-in account.
default
Section titled “default”Request error
object
object
Stable; branch on it. Any operation can answer invalid_request, with param naming the refused field when there is one; human_session_required, when an API key, service account or workload calls an operation only a signed-in person may perform; reauthentication_required, when a person’s sign-in is too old for the operation; permission_denied; route_not_found and method_not_allowed, when no operation matches the path or method; and feature_unavailable, when the operation’s service is not enabled on this deployment.
The request field a refusal is about, such as the agent_id or run_id query parameter; null when the refusal is not about one field.
Example
{ "error": { "action": "sign_in" }}