Start a pending action
Start the action identified by the URL. Both cue_id and secret are obtained from the action’s resolution_link.url; the secret is a signed token bound to a member and expires 1 hour after it is issued.
The body must include the parameters listed in the action’s resolution_link.required_parameters. The body and response shapes are action-specific — the documented schemas apply when the action’s code is reauthenticate. Other action codes will use their own request/response shapes.
Once started, the action stays in progress until its outcome is reported via /cues/{cue_id}/state.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Path Parameters
The action's ID
Query Parameters
Signed secret authorising the caller for this action
Body
Body shape for resolving an action whose code is reauthenticate.
Other action codes will introduce their own input schemas — do not assume this schema applies to every action.
URL the end-user should land on after the reauthentication completes successfully.
URL the end-user should land on if they cancel or the reauthentication fails.
Optional IETF language tag (e.g. en, de) used to localise the reauthentication UI.
Optional caller location metadata recorded alongside the start event.
Optional caller client metadata (user-agent, device, etc.) recorded alongside the start event.
Response
OK
Response shape for resolving an action whose code is reauthenticate.
URL the caller should redirect the end-user to in order to complete the reauthentication flow.