Usage
Endpoint Usage
Retrieve org-wide API usage metrics for the endpoints available to your organization
GET
Overview
The Endpoint Usage endpoint returns organization-wide usage metrics for the Minerva API endpoints your organization is allowed to access. Each result is grouped by endpoint, such asv1/resolve or v2/enrich, and includes aggregate counts for:
- Total requests
- Total input records
- Total resolvable records
- Total matches
- Computed match rates
- Last request timestamp
start_date and end_date, the response also includes a buckets array for each endpoint so you can chart usage over time.
Request
Headers
Your API key for authentication.
Query Parameters
Optional start date in
YYYY-MM-DD format. Must be provided together with end_date. When both dates are present, the response includes bucketed usage data.Optional end date in
YYYY-MM-DD format. Must be provided together with start_date. The date range is inclusive in the requested timezone.Optional bucket frequency. Supported values are
hour, day, week, month, quarter, and year. Defaults to day.Optional IANA timezone name, such as
UTC or America/New_York. Defaults to UTC.Optional flag indicating whether endpoints with zero usage should be included in the response. Defaults to
false.Request Notes
- There is no request body.
start_dateandend_datemust be supplied together or omitted together.
Response
Success Response
Unique identifier for this request, useful for support and debugging.
Array of endpoint usage summary objects for the requester’s organization.
ISO 8601 timestamp indicating when the request finished.
Result Object
Endpoint identifier in
version/path format, such as v1/resolve or v2/enrich.Total number of API requests made to this endpoint for the selected organization and date range.
Total number of input records submitted to this endpoint.
Total number of records that were considered resolvable for this endpoint.
Total number of matched records produced by this endpoint.
Computed as
num_matches / num_input_records. Returns 0.0 when no input records exist.Computed as
num_matches / num_resolvable_records. Returns 0.0 when no resolvable records exist.Timestamp of the most recent request for this endpoint in the selected range. Can be
null for unused endpoints when include_unused_endpoints=true.Array of bucket objects when both
start_date and end_date are provided. Otherwise this field is null.Bucket Object
Start timestamp for the bucket in the requested timezone.
Number of requests in this bucket.
Number of input records in this bucket.
Number of resolvable records in this bucket.
Number of matched records in this bucket.
Behavior Notes
- Results are returned at the organization level, not the individual user level.
- If you omit the date range, aggregate totals are still returned, but
bucketswill benull. - If
include_unused_endpoints=true, endpoints with no usage can be returned with zero counts andlast_requested_at: null. - Results are sorted by
num_matchesin descending order.
Error Responses
Common Errors
400- Bad Request: Invalid timezone, only one ofstart_dateorend_datewas supplied, or the requester organization could not be determined401- Unauthorized: Invalid or missing API key405- Method Not Allowed: Using a method other thanGET422- Unprocessable Entity: Invalid query parameter type or unsupportedbucketing_size500- Internal Server Error: Unexpected server error