Skip to main content
GET /v1/projects/{id}/platforms/operations/{operationId} Reads one operation using the same operation representation as creation and list. The API includes detail.setupUrl only with platforms:write for this project. This is the polling endpoint every asynchronous request here points its Location at, and it resolves from the moment that request is accepted — an operation is committed before its work is dispatched, so there is no window in which the URL 404s. Poll until state is one of succeeded, failed or cancelled, pacing from the Retry-After the accepting response returned. While an email domain waits for DNS, detail always contains the manual records and may additionally contain automaticSetup with a signed provider URL to open separately. Once the operation has produced a resource, the response carries that resource too, so the poll that finishes is also the one that tells you what you got. succeeded means the work is done; billing runs behind it and is not something the caller waits on. Operations are never purged, so a 404 means the id was never this project’s. Requires the platforms:read permission bound to the project resource in the path.
TypeScript

Parameters

string
required
string
required

Returns

200 The operation, and the resource it produced once one exists. Retry-After is supplied for pending/running campaign and Telegram operations and omitted once terminal. GetOperationResponse Headers: Cache-Control. The raw response carries these headers; see Raw responses.
Operation
required
Resource