Person Search
Person Search Usage
Retrieve your organization’s daily person-search delivery limits, current-day consumption, and recent per-day history
GET
Overview
The Person Search Usage endpoint returns quota and consumption metrics scoped to the organization associated with your API key. Use it to:- Check today’s remaining record budget before issuing additional searches
- Power a usage dashboard or chart day-over-day trends
- Reconcile internal billing records against delivered record counts
history represents a single UTC calendar day, with counts for:
records_delivered- PIDs delivered in search responsessearches_created- number ofPOST /person-search/v0/searchcalls that produced a stored searchparse_requests- natural-language query parses performed for searches
Request
Headers
string
required
Your API key for authentication.
Query Parameters
integer
default:"30"
Number of UTC calendar days of history to include, counting back from today (inclusive). Must be between
1 and 90. Defaults to 30.Request Notes
- There is no request body.
- The date range is always anchored to today (UTC) and cannot be customized beyond
days.
Response
Success Response
string
UUID of the organization associated with your API key.
integer
Maximum number of person records that can be delivered per UTC day for your organization.
integer
Records delivered so far today (UTC day). Counts toward
daily_record_limit.integer
Remaining record budget for today, computed as
max(0, daily_record_limit - current_day_records_delivered).array
Array of
DailyUsage objects, one per UTC calendar day in the requested window. See Daily usage object below.Daily usage object
string
UTC calendar date for this row, in
YYYY-MM-DD format.integer
Number of person records delivered by the person search API on that day.
integer
Number of
POST /person-search/v0/search calls that produced a stored search on that day.integer
Natural-language query parse requests processed on that day.
Behavior Notes
- Results are scoped to the organization associated with your API key.
- All dates and day boundaries are in UTC.
current_day_records_deliveredis the same value that appears in thehistoryrow whoseperiod_startequals today’s UTC date.- Days with no activity are included in
historywith zeroed counters, so the array length is always equal to the requesteddaysvalue. current_day_remainingis clamped at zero; it never goes negative even if delivery briefly exceeds the daily limit.
Error Responses
Common Errors
401- Unauthorized: Invalid or missing API key403- Forbidden: The API key is valid but not authorized for this route or your plan tier422- Unprocessable Entity:daysis not an integer, or is outside the allowed range1-90429- Too Many Requests: Rate limit or plan quota exceeded500- Internal Server Error: Unexpected server error
Error Example
Out-of-rangedays:
Common Integration Patterns
Check remaining budget before a large search job:Related Endpoints
- Person Search - Create a new person search
- Get Person Search - Retrieve a previously created search by id
- Endpoint Usage - Org-wide usage metrics across other Minerva endpoints