Google

Chrome Verified Access API

API for Verified Access chrome extension to provide credential verification for chrome devices connecting to an enterprise network

Identity & security#openapi#analytics#media

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

API for Verified Access chrome extension to provide credential verification for chrome devices connecting to an enterprise network

Endpoints 2

challenge

  • POSTGenerates a new challenge./v2/challenge:generateGenerates a new challenge.
  • POSTVerifies the challenge response./v2/challenge:verifyVerifies the challenge response.

API details

Base URL
https://verifiedaccess.googleapis.com
Authentication
OAuth 2.0 (authorization code flow) with 1 scope
An API key in the key query parameter
Operations
2 operations on 2 pathsPOST 2
Main resources
challenge 2
Response formats
application/json
Description format
Google API Discovery, API version v2

How to test the Chrome Verified Access API in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Chrome Verified Access API collection, without the publisher's secrets.
  3. Add your credentialsThis API uses OAuth 2.0 (authorization code flow) with 1 scope. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “Generates a new challenge.” (POST /v2/challenge:generate), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Chrome Verified Access API?

API for Verified Access chrome extension to provide credential verification for chrome devices connecting to an enterprise network It is listed under Identity & security and has 2 endpoints.

Who publishes the Chrome Verified Access API?

It is listed from Google's public API description (an OpenAPI document), not published by Google on Swastik Codes. Anyone who controls googleapis.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Chrome Verified Access API?

Requests go to https://verifiedaccess.googleapis.com. Endpoint paths are added to this base URL.

How do I authenticate with the Chrome Verified Access API?

It accepts 2 methods: OAuth 2.0 (authorization code flow) with 1 scope; an API key in the key query parameter.

How many endpoints does the Chrome Verified Access API have?

2 operations on 2 paths (2 POST). The largest groups are challenge.

Is forking the Chrome Verified Access API free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.