PAGES

Claim history

The `POST /api/v1/tokens/github` and `POST /api/v1/tokens/google` endpoints now reject caller-supplied `access_token` or `id_token` values; callers must pass an OAuth authorization code instead. Our best guess
Claim history
  1. Revision 1 · · Our best guess

    The `POST /api/v1/tokens/github` and `POST /api/v1/tokens/google` endpoints now reject caller-supplied `access_token` or `id_token` values; callers must pass an OAuth authorization code instead.

    machine summarizer

Saved in this browser. Sign in to sync your tools.