getNotificationPushOperation
const url = 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/notification-push/operations/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0?mode=test&reset_generation=1';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/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/notification-push/operations/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0?mode=test&reset_generation=1' \ --header 'Authorization: Bearer <token>'Human-session Web Push device lifecycle. Exact account, organization, environment, mode and reset are checked; mutation also requires recent local sign-in. Browser endpoint, auth secret and P-256 key are transient registration intake only and never returned by metadata APIs. The reviewed public VAPID key, enrolled provider and explicit maximum-30-day deadline are immutable. At most eight unexpired devices per account/environment. Preserve exact UUID key and metadata after unknown results; inspect its operation receipt before an explicit retry. A receipt is historical, not current usability. Push category preferences are separate opt-in; Test delivery is intercepted. No external provider or browser installation acceptance is implied.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Responses
Section titled “Responses”Safe current metadata or immutable historical operation metadata.
object
Example
{ "mode": "test", "state": "active"}Headers
Section titled “Headers”default
Section titled “default”Request refused or service 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" }}