Wait for operation
Block until a long-running operation is done
/api/v2/operations/{operation}:waitAuthentication WLT-Api-Key
Block for up to the server cap, then inspect done. A successful wait can still return a running operation, so keep a polling fallback. Read the guide.
Path parameters
operationstringrequiredRequest body
application/json
timeoutSecsinteger | nullSeconds to block waiting for the operation to finish, capped server-side at 30; omit to use the cap. Best-effort: the operation may still be running when this returns.
1 <= valueResponses
200
Successful Response
application/json
An operation with its result, available through singular reads.
idstringrequiredShort operation id used in /operations/{operation} paths.
ownerIdstringrequiredAccount that owns the operation.
metadataobject | nullTask information and optional progress details. Use metadata.task to interpret a generic operation response, and use done to determine completion.
donebooleanrequiredWhether the operation is terminal. When true, a non-null error indicates failure; otherwise the operation succeeded.
errorOperationError | nullFailure details when done is true and the task failed; null while running and after success.
expiresAtSecsinteger | nullTask execution deadline as Unix seconds, when one is exposed. This is not an asset URL expiration.
createdAtSecsinteger | nullUnix seconds when the operation was accepted.
responseobject | nullTask-specific result when done is true and the task succeeded; null while running and after failure.
namestringrequiredFull resource name for the operation.
For project operations:
accounts/{account}/projects/{project}/operations/{operation}.
Operation paths accept the short id.
422
Validation Error
application/json
detailarray<ValidationError>