List the campaigns you created
const url = 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/evaluation-calibrations';const options = {method: 'GET', headers: {cookie: 'katara_session=<katara_session>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/evaluation-calibrations \ --cookie katara_session=<katara_session>Requires a current human session; API keys, services and workloads are refused, and so is a role that cannot read the datasets and scores a campaign is built from. Lists only campaigns you created in the current reset generation, with the certificate that sealed each one. The list does not rebuild each campaign from its sources, so reading one can still be refused after its sources were withdrawn.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Header Parameters
Section titled “Header Parameters”Optional mounted-account binding for cookie reads. A supplied different account returns account_changed.
Responses
Section titled “Responses”Your campaigns in the current generation, newest first.
object
Enough to pick a campaign again. No score, label or reviewer is included.
object
The held-out dataset versions the campaign pins.
object
Present once the campaign is sealed.
Example
{ "data": [ { "state": "open" } ]}Headers
Section titled “Headers”Account_changed: reload and review with the signed-in account.
default
Section titled “default”Request rejected or unavailable.
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" }}