Flock Safety · OAuth Scopes

Flock Safety OAuth Scopes

OAuth 2.0 searched

Flock Safety publishes 5 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Flock Safety API on a user’s behalf.

Tokens are issued from https://api.flocksafety.com/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyAmerican DynamismPublic SafetyLaw EnforcementLicense Plate RecognitionLPRPhysical SecuritySurveillanceComputer VisionWebhooksGeolocationCAD

Scopes: 5 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://api.flocksafety.com/oauth/token

Flows
clientCredentials

Scopes (5)

Scope	Description	Flows
custom-hotlists:read	Read access to custom hotlists (canonical spelling used in operation security requirements).	clientCredentials
custom-hotlists:write	Write access to custom hotlists (canonical spelling used in operation security requirements).	clientCredentials
custom-holists:read	Read access to custom hotlists (verbatim from oauth2Auth scheme; note the source typo "holists").	clientCredentials
custom-holists:write	Write access to custom hotlists (verbatim from oauth2Auth scheme; note the source typo "holists").	clientCredentials
plate-reads:lookup	Access to perform lookups on license plate reads.	clientCredentials

📄 Provider scope reference: https://docs.flocksafety.com/developer-hub/docs/client-credentials

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: openapi/flock-safety-openapi-original.yml
docs: https://docs.flocksafety.com/developer-hub/docs/client-credentials
notes: >-
  Scopes are declared per OAuth application when Flock registers an integration; they govern what a
  Flock App can access. The oauth2Auth scheme in the spec spells the hotlist scopes 'custom-holists:*'
  (a source typo, missing a 't'), while operation security requirements use 'custom-hotlists:*'. Both
  spellings are preserved below; treat 'custom-hotlists:*' as canonical.
schemes:
- name: oauth2Auth
  source: openapi/flock-safety-openapi-original.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.flocksafety.com/oauth/token
- name: FlockOAuth
  source: openapi/flock-safety-openapi-original.yml
  description: OAuth 2 with the client credentials flow
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.flocksafety.com/oauth/token
- name: oauth2
  source: openapi/flock-safety-openapi-original.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.flocksafety.com/oauth/token
scopes:
- scope: custom-hotlists:read
  description: Read access to custom hotlists (canonical spelling used in operation security requirements).
  flows: [clientCredentials]
  sources: [openapi/flock-safety-openapi-original.yml]
- scope: custom-hotlists:write
  description: Write access to custom hotlists (canonical spelling used in operation security requirements).
  flows: [clientCredentials]
  sources: [openapi/flock-safety-openapi-original.yml]
- scope: custom-holists:read
  description: 'Read access to custom hotlists (verbatim from oauth2Auth scheme; note the source typo "holists").'
  flows: [clientCredentials]
  sources: [openapi/flock-safety-openapi-original.yml]
- scope: custom-holists:write
  description: 'Write access to custom hotlists (verbatim from oauth2Auth scheme; note the source typo "holists").'
  flows: [clientCredentials]
  sources: [openapi/flock-safety-openapi-original.yml]
- scope: plate-reads:lookup
  description: Access to perform lookups on license plate reads.
  flows: [clientCredentials]
  sources: [openapi/flock-safety-openapi-original.yml]