How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Flock Safety Plate Reads API

The Plate Reads API from Flock Safety — 2 operation(s) for plate reads.

Flock Safety Plate Reads API is one of 10 APIs that Flock Safety publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Plate Reads. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 2 operations across 2 paths, and defines 15 schemas. It is described by OpenAPI 3.0.3, at version 3.0.0.

Requests are made against 2 base URLs: https://api.flocksafety.com/api/v3, https://dev-api.flocksafety.com/api/v3.

2 operations 2 paths 15 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
3.0.0
Base URL
https://api.flocksafety.com/api/v3
Authentication
HTTP Bearer, OAuth 2.0, OAuth 2.0, OAuth 2.0
Resource Areas
1

Authentication & Security 4

Flock Safety Plate Reads API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It supports OAuth 2.0 (oauth2Auth) using the clientCredentials flow, exposing 2 scopes. It supports OAuth 2.0 (FlockOAuth) using the clientCredentials flow, exposing 1 scope. It supports OAuth 2.0 (oauth2) using the clientCredentials flow.

  • FlockOAuth — OAuth 2 with the client credentials flow

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Plate Reads 2
GET
/reads/lookup/page/{pageId}
View license plate reads lookup results
1 param → 200401403422429
POST
/reads/lookup
Lookup license plate reads
body → 200400401403422429

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are LookupRequest (11 properties), Device (9 properties), Location (8 properties), LicensePlateRead (6 properties). Each schema is shown below with its type and property counts.

LookupRequest
object
A request to lookup license plate reads.
11 properties 4 required
Network
object
The network that the device belongs to.
2 properties 2 required
LicensePlateRead
object
A license plate read
6 properties 4 required
ErrorResponse
object
1 property
Location
object
either latitude and longitude is required, or one of streetAddress/city/state
8 properties
SortCriteria
object
2 properties 2 required
Device
object
9 properties 8 required
RadiusFilter
object
Filters the results to where only reads captured within this radius will be returned.
1 property
AdditionalMetadata
object
flat json object, defaults to {} and returned as {} if not provided
2 properties
LookupResult
object
Results
4 properties 2 required
DeviceType
string
The device's type.
StateInfo
object
2 properties 2 required
ConfidenceFilter
object
2 properties 2 required
AreaFilter
object
Filters the results to where only reads captured within an area will be returned. The area must be defined as a [GeoJSON Polygon with a single ring](https://ma…
1 property
PlateInfo
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flock-safety-plate-reads-api-openapi.yml Raw ↑

Other APIs Flock Safety publishes across the network.

Flock Safety Alerts API
Flock Safety CAD Events API
Flock Safety Custom Hotlists API
Flock Safety Devices API
Flock Safety LPR Hotlist Alert Subscriptions API
Flock Safety OAuth2 API
Flock Safety Tracked Subject Types API
Flock Safety Tracked Subjects API
Flock Safety Vehicle Images API
Where this information came from

This is an independent, third-party profile of Flock Safety Plate Reads API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.