Google

Security Token Service API

The Security Token Service exchanges Google or third-party credentials for a short-lived access token to Google Cloud resources.

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

The Security Token Service exchanges Google or third-party credentials for a short-lived access token to Google Cloud resources.

Endpoints 3

projects.locations.workloadIdentityPools.openid

  • GETFetches the signing keys for an agentic or managed workload identity pool and returns them in JWK Set format, defined…/v1/:name/openid/jwksFetches the signing keys for an agentic or managed workload identity pool and returns them in JWK Set format, defined in RFC 7517. For now, only agentic…

projects.locations.workloadIdentityPools.well-known

  • GETGets the OIDC provider configuration for an agentic or managed workload identity pool following [the OIDC 1.0…/v1/:name/.well-known/openid-configurationGets the OIDC provider configuration for an agentic or managed workload identity pool following the OIDC 1.0 discovery specification. For now, only agentic…

v1

  • POSTExchanges a credential for a Google OAuth 2.0 access token/v1/tokenExchanges a credential for a Google OAuth 2.0 access token. The token asserts an external identity within an identity pool, or it applies a Credential Access…

API details

Base URL
https://sts.googleapis.com
Authentication
OAuth 2.0 (authorization code flow)
An API key in the key query parameter
Operations
3 operations on 3 pathsGET 2POST 1
Main resources
projects.locations.workloadIdentityPools.openid 1projects.locations.workloadIdentityPools.well-known 1v1 1
Response formats
application/json
Description format
Google API Discovery, API version v1

How to test the Security Token Service 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 Security Token Service API collection, without the publisher's secrets.
  3. Add your credentialsThis API uses OAuth 2.0 (authorization code flow). Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “Fetches the signing keys for an agentic or managed workload identity pool and returns them in JWK Set format, defined…” (GET /v1/:name/openid/jwks), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Security Token Service API?

The Security Token Service exchanges Google or third-party credentials for a short-lived access token to Google Cloud resources. It is listed under Identity & security and has 3 endpoints.

Who publishes the Security Token Service 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 Security Token Service API?

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

How do I authenticate with the Security Token Service API?

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

How many endpoints does the Security Token Service API have?

3 operations on 3 paths (2 GET, 1 POST). The largest groups are projects.locations.workloadIdentityPools.openid, projects.locations.workloadIdentityPools.well-known, v1.

Is forking the Security Token Service 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.