Read historical promotion receipt
const url = 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environment-promotions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/reviews/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/receipt';const options = {method: 'GET', headers: {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 GET \ --url https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environment-promotions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/reviews/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/receipt \ --header 'Authorization: Bearer <token>'Requires a signed-in human owner session and current owner authority in both the source Test and destination Live environments of this organization. API keys, service identities and workloads are refused. Environment bindings come from the immutable record; query parameters are not accepted. Responses are no-store. The routes are present only when the promotion service is configured. Canonical approved evidence and current binding verification are mandatory for readiness and activation; uncalibrated scores or a statistics threshold alone never authorize activation. Returns only immutable operation/version/scope metadata under current owner authority. A historical receipt does not claim the published version is currently usable; it excludes former content references, private request material and secrets.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Header Parameters
Section titled “Header Parameters”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
object
object
object
object
Example
{ "source_mode": "test", "destination_mode": "live", "completed": true}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" }}