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 LPR Hotlist Alert Subscriptions API

The LPR Hotlist Alert Subscriptions API from Flock Safety — 2 operation(s) for lpr hotlist alert subscriptions.

Flock Safety LPR Hotlist Alert Subscriptions 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 LPR Hotlist Alert Subscriptions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 5 operations across 2 paths, and defines 4 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.

5 operations 2 paths 4 schemas 1 DELETE2 GET1 POST1 PUT

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 LPR Hotlist Alert Subscriptions 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 5

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

LPR Hotlist Alert Subscriptions 5
DELETE
/integrations/lpr/alerts/subscriptions/{id}
Delete Subscription
1 param → 204403404500
GET
/integrations/lpr/alerts/subscriptions/{id}
Get Subscription
1 param → 200403404500
GET
/integrations/lpr/alerts/subscriptions
Get Subscriptions
→ 200403500
POST
/integrations/lpr/alerts/subscriptions
Create Subscription
body → 201400403409500
PUT
/integrations/lpr/alerts/subscriptions
Update Subscription
body → 200400403404500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are CreateSubscriptionRequest (7 properties), Credentials (4 properties). Each schema is shown below with its type and property counts.

UpdateSubscriptionRequest
object
request body schema to update an existing webhook subscription
CreateSubscriptionRequest
object
request body schema to create a new webhook subscription
7 properties 3 required
Credentials
object
authentication details for calling the webhook endpoint
4 properties 1 required
Subscription
object
response object when creating, updating or fetching a webhook subscription

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flock-safety-lpr-hotlist-alert-subscriptions-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 OAuth2 API
Flock Safety Plate Reads 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 LPR Hotlist Alert Subscriptions 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.