Skip to main content
GET

Quick Answer

How do I see my person-search usage? Use this endpoint to check your organization’s daily record-delivery limit, how many records you’ve already been charged for today, how much of the daily budget is remaining, and a per-day history of search activity.Common questions this endpoint answers:
  • What’s my daily person-search record limit?
  • How many records have I been delivered today?
  • How much quota do I have left for today?
  • How many searches did we run per day over the last month?
  • How many natural-language parse requests did we consume per day?
What you get back: The org’s daily_record_limit, records delivered today, remaining budget today, and a per-UTC-day history array with delivered record counts, searches created, and parse requests.

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
Each row of history represents a single UTC calendar day, with counts for:
  • records_delivered - PIDs delivered in search responses
  • searches_created - number of POST /person-search/v0/search calls that produced a stored search
  • parse_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_delivered is the same value that appears in the history row whose period_start equals today’s UTC date.
  • Days with no activity are included in history with zeroed counters, so the array length is always equal to the requested days value.
  • current_day_remaining is 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 key
  • 403 - Forbidden: The API key is valid but not authorized for this route or your plan tier
  • 422 - Unprocessable Entity: days is not an integer, or is outside the allowed range 1-90
  • 429 - Too Many Requests: Rate limit or plan quota exceeded
  • 500 - Internal Server Error: Unexpected server error

Error Example

Out-of-range days:

Common Integration Patterns

Check remaining budget before a large search job:
Build a day-over-day consumption chart: