AI-generated Key Takeaways
-
The
challenge.create
API is accessed via aPOST
request tohttps://verifiedaccess.googleapis.com/v1/challenge
and uses gRPC Transcoding syntax. -
The request body must be empty, while the response body contains a
challenge
and may optionally contain analternativeChallenge
, both formatted as SignedData objects. -
This API requires the
https://www.googleapis.com/auth/verifiedaccess
OAuth scope for authorization.
challenge.create API
HTTP request
POST https://verifiedaccess.googleapis.com/v1/challenge
The URL uses gRPC Transcoding syntax.
Request body
The request body must be empty.
Response body
Result message for VerifiedAccess.CreateChallenge.
If successful, the response body contains data with the following structure:
JSON representation |
---|
{ "challenge": { object ( |
Fields | |
---|---|
challenge |
Generated challenge |
alternativeChallenge |
Challenge generated with the old signing key (this will only be present during key rotation) |
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/verifiedaccess
For more information, see the OAuth 2.0 Overview.