Google Authentication

It is possible to use Google Sign-In for authentication with the Verifiable API. In order to do so we follow the Google Sign-In for server-side apps flow. In order to use this flow you must use the client ID from Verifiable when signing in to Google and send the authorization code as payload to this endpoint. In return you will receive an access token that can be used in the following API calls. The email address of the user must already be registered at Verifiable.

Request
Request Body schema: application/json
object (SensitiveString)

If includeSensitiveInfo query parameter set to true the value will be shown in the response, otherwise it will be masked with *.

timeToLive
string <timespan>

If set, the created token will expire after the duration specified by this parameter. Note that the token will still be expired after 4 weeks of no use, regardless of the time to live. Additionally there might be a limit set for your organization. If the requested time-to-live exceeds this limit the token will be capped to that limit.

object (SensitiveString)

If includeSensitiveInfo query parameter set to true the value will be shown in the response, otherwise it will be masked with *.

Responses
200

Success

400

Bad Request

401

Unauthorized

403

Forbidden

500

Server Error

post/auth/token/google
Request samples
application/json
{
  • "code": "4/yU4cQZT...4z7U4UmAI",
  • "timeToLive": "00:30:00"
}
Response samples
application/json
{
  • "tokenId": "0847312d-19fe-49d2-9e21-5825735b511a",
  • "token": "MtetyFcIW...xgXXX-Z4yy"
}