Skip to main content
GET

Quick Answer

How do I see API usage for my organization? Use this endpoint to retrieve org-wide usage metrics for the Minerva API endpoints your organization can access.Common questions this endpoint answers:
  • Which Minerva endpoints has my organization used?
  • How many requests did we make to each endpoint?
  • How many input records, resolvable records, and matches did each endpoint produce?
  • When was each endpoint last used?
  • How can I get usage buckets over time for reporting?
What you get back: A list of endpoint-level usage summaries for your organization, with optional time buckets when you provide a date range.

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 as v1/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
If you provide both start_date and end_date, the response also includes a buckets array for each endpoint so you can chart usage over time.

Request

Headers

string
required
Your API key for authentication.

Query Parameters

string
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.
string
Optional end date in YYYY-MM-DD format. Must be provided together with start_date. The date range is inclusive in the requested timezone.
string
Optional bucket frequency. Supported values are hour, day, week, month, quarter, and year. Defaults to day.
string
Optional IANA timezone name, such as UTC or America/New_York. Defaults to UTC.
boolean
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_date and end_date must be supplied together or omitted together.

Response

Success Response

string
Unique identifier for this request, useful for support and debugging.
array
Array of endpoint usage summary objects for the requester’s organization.
string
ISO 8601 timestamp indicating when the request finished.

Result Object

string
Endpoint identifier in version/path format, such as v1/resolve or v2/enrich.
integer
Total number of API requests made to this endpoint for the selected organization and date range.
integer
Total number of input records submitted to this endpoint.
integer
Total number of records that were considered resolvable for this endpoint.
integer
Total number of matched records produced by this endpoint.
number
Computed as num_matches / num_input_records. Returns 0.0 when no input records exist.
number
Computed as num_matches / num_resolvable_records. Returns 0.0 when no resolvable records exist.
string
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
Array of bucket objects when both start_date and end_date are provided. Otherwise this field is null.

Bucket Object

string
Start timestamp for the bucket in the requested timezone.
integer
Number of requests in this bucket.
integer
Number of input records in this bucket.
integer
Number of resolvable records in this bucket.
integer
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 buckets will be null.
  • If include_unused_endpoints=true, endpoints with no usage can be returned with zero counts and last_requested_at: null.
  • Results are sorted by num_matches in descending order.

Error Responses

Common Errors

  • 400 - Bad Request: Invalid timezone, only one of start_date or end_date was supplied, or the requester organization could not be determined
  • 401 - Unauthorized: Invalid or missing API key
  • 405 - Method Not Allowed: Using a method other than GET
  • 422 - Unprocessable Entity: Invalid query parameter type or unsupported bucketing_size
  • 500 - Internal Server Error: Unexpected server error

Error Examples

Only one date provided:
Invalid timezone:

Common Integration Patterns

Pattern 1: Daily endpoint usage dashboard
Pattern 2: Discover all available endpoints for your org