Toast · Authentication Profile

Toast Authentication

Authentication

Toast secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

Food ServicePoint of SaleRestaurantsHospitality
Methods: oauth2 Schemes: 1 OAuth flows: clientCredentials API key in:

Security Schemes

oauth2 oauth2
· flows: clientCredentials

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/toast-labor-openapi.yaml, openapi/toast-menus-openapi.yaml, openapi/toast-orders-openapi.yaml,
  openapi/toast-partners-openapi.yaml, openapi/toast-restaurants-openapi.yaml, openapi/toast-stock-openapi.yaml
summary:
  types:
  - oauth2
  oauth2_flows:
  - clientCredentials
schemes:
- name: oauth2
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://toast-api-server/authentication/v1/authentication/login
    scopes: 7
  description: "Access to Toast APIs, specific endpoints, \nand specific API endpoint operations\
    \ is \ncontrolled by the scopes that are associated \nwith your API account. \nA full reference\
    \ for Toast API scopes and \ntheir capabilities can be found in the\n[_Toast Developer Guide_](https://doc.toasttab.com/doc/devguide/apiScopes.html)."
  sources:
  - openapi/toast-labor-openapi.yaml
  - openapi/toast-menus-openapi.yaml
  - openapi/toast-orders-openapi.yaml
  - openapi/toast-partners-openapi.yaml
  - openapi/toast-restaurants-openapi.yaml
  - openapi/toast-stock-openapi.yaml