ALPR reads API data source settings in the Third-Party ALPR plugin - Configure an ALPR reads API data source so that the Third-Party ALPR plugin can ingest data from your network of third-party on-premises cameras. - Third-Party ALPR 5.10.11.0 - Plugin and extension guides

Genetec™ Third-Party ALPR Plugin Guide 5.10.13.0
Product
Third-Party ALPR
Content type
Guides > Plugin and extension guides
Version
5.10
Release
5.10.13.0
ft:locale
en-US
Last updated
2026-08-25

Configure an ALPR reads API data source so that the Third-Party ALPR plugin can ingest data from your network of third-party on-premises cameras.

Setting Description
Name Select a name for the data source that identifies where license plate data is coming from.
Raise 'no data' events Set the time threshold after which a custom Security Center event is triggered if no data is received from the specified data source. For more information, refer to Creating event-to-actions.
Anonymized raw data logging Select this setting to make the data source log raw data with the license plate anonymized.
NOTE: Raw data consists of the exact and unprocessed data that is received from the relevant camera or API. Some private fields are still anonymized for privacy reasons.
API path prefix (Optional) If you want to use multiple instances of Genetec™ Third-Party ALPR with different endpoints, configure a prefix in the API path prefix field.
NOTE: You might want to use multiple plugin instances to do load balance the cameras or data sources. For example, you might have one plugin instance for Vigilant on one server and another plugin on another server for Safefleet.
REST port Configure the port where the REST API listens for requests. The default port is 443.
API documentation Select whether the plugin enables an endpoint to access the API documentation and displays a link to the API. This feature should be disabled in production environments.
Effective v1 address (Reads only) Provide the path used to send ALPR reads to the plugin. This is usually a camera that sends only reads to your system.
NOTE:
  • This address assumes that you are presently running the same server where the plugin is running. If you are using a different machine, copy this URL and replace localhost with the IP of the server running the plugin role.
  • The default value is https://<hostname>/api/v1/LprPlugin/LprIngestion/reads
Effective v2 address (Reads and Hits) Provide the path used to send ALPR reads and hits to the plugin. This is usually a cloud service that sends the reads and hits along with the hotlist it is matched against.
NOTE:
  • This address assumes that you are presently running the same server where the plugin is running. If you are using a different machine, copy this URL and replace localhost with the IP of the server running the plugin role.
  • The default value is https://<hostname>/LprPlugin/api/v2/LprIngestion/event
Advanced settings
Maximum message rate (v2 only) Set the maximum number of requests a data source can process in one second. This limit helps prevent system overload. If data arrives at a rate faster than specified here, some requests will be rejected.
v2 authentication mode Select the authentication mode required.
  • Choose Security Center token if you are using on-premises cameras.
    NOTE: You must possess the following privileges to apply the Security Center token authentication mode:
    • Web App
    • Log on using SDK
    • Third-party ALPR reads API
  • Use OAuth token if you are using a cloud-based ALPR provider.
    NOTE: If you select OAuth token, you must add your OAuth credentials and then click Apply.