One secure sign-in session's steps
One secure sign-in session's steps: CustomDomain™ API reference in the analytics group. Covers request parameters, the request body, responses and error codes.
The session's row plus its steps in order, each with the seconds since the session started, so one slow or failed run can be read. A step is a word from a fixed list (a state the session moved to, or a step the sign-in window reported), with the failure it ended in, if any, and one short detail word. It never holds a code, a password, a domain or anything typed. 404 for a session of another workspace. API key; any member role.
Authorization
apiKey Long-lived tenant API key, cd_live_… (production) or cd_test_… (staging, development), stored hashed. Keys created before the switch to cd_ start with sk_live_… / sk_test_… and are still accepted. Scoped to the owning application's tenant.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/analytics/secure-sign-in/sessions/string"{ "id": "string", "provider": "string", "connection_id": "string", "started_at": "2019-08-24T14:15:22Z", "outcome": "done", "reached": "started", "stop": "string", "last_step": "string", "total_seconds": 0, "ended_at": "2019-08-24T14:15:22Z", "failure": "string", "events": [ { "step": "string", "seconds_since_start": 0, "failure": "string", "detail": "string" } ]}{ "code": "string", "title": "string", "details": "string"}{ "code": "string", "title": "string", "details": "string"}