ORory
frontend

Submit a FedCM token

Changed on

Use this endpoint to submit a token from a FedCM provider through navigator.credentials.get and log the user in. The parameters from navigator.credentials.get must have come from GET self-service/fed-cm/parameters.

post/self-service/fed-cm/token

Request

  • Base URL
    / (relative, and the document was published on a file host, not at the API’s origin)
  • URL
    /self-service/fed-cm/token
  • Auth
    none declared

Request body

csrf_tokenstring required

CSRFToken is the anti-CSRF token.

noncestring

Nonce is the nonce that was used in the navigator.credentials.get call. If specified, it must match the nonce claim in the token.

tokenstring required

Token contains the result of navigator.credentials.get.

transient_payloadobject

Transient data to pass along to any webhooks.

Response

successfulNativeLogin

continue_withContinueWith[]

Contains a list of actions, that could follow this flow

It can, for example, this will contain a reference to the verification flow, created as part of the user's registration or the token of the session.

session_tokenstring

The Session Token

A session token is equivalent to a session cookie, but it can be sent in the HTTP Authorization Header:

Authorization: bearer ${session-token}

The session token is only issued for API flows, not for Browser flows!

Example response

{
  "session": {
    "identity": {
      "verifiable_addresses": [
        {
          "created_at": "2014-01-01T23:28:56.782Z",
          "updated_at": "2014-01-01T23:28:56.782Z",
          "verified": true,
          "via": "email"
        }
      ]
    }
  }
}

Changes