API Reference
API reference for the /plate-reads route
The /plate-reads
endpoint is used to ingest ALPR data and is the primary public endpoint used to interact with external systems. This document outlines the expected request format and available fields.
Authentication
All requests require an API key sent in the header.
Request Format
The API accepts JSON payloads with the following fields:
Field | Type | Required | Description |
---|---|---|---|
ai_dump | Object | No* | Object containing AI model predictions from CPAI (preferred method). |
memo | String | No* | Comma-separated list of detections with confidence (DEPRECATED). |
plate_number | String | No* | Direct plate number input (DEPRECATED). |
timestamp | String | No | ISO 8601 timestamp of when the plate was detected. Defaults to current time if not provided. |
camera | String | No | Name or identifier of the camera that captured the plate. |
Image | String | No | Base64 encoded JPEG of the plate detection. |
ALERT_CLIP | String | No | Blue Iris alert clip identifier. |
ALERT_PATH | String | No | Blue Iris alert path. |
*At least one of ai_dump
, memo
, or plate_number
is required. memo
is
entirely deprecated. plate_number
should only be used be non
natively-supported AI systems.
Plate Information Methods
The API supports three different methods for providing plate information:
1. AI Dump Format
2. Memo Format
The system will extract license plates from the memo, filtering out non-plate objects.
3. Direct Plate Number
Response Format
Success Response (201 Created)
Duplicate Response (409 Conflict)
Error Response (400/401/500)
Notes
- Plate numbers are automatically converted to uppercase
- Duplicate detections (same plate at same timestamp) are automatically filtered
- The system supports ignoring specific plates based on your configuration
- Images are saved to disk if provided, with both full-size and thumbnail versions