Get usage metrics for the Glacier API

get

https://glacier-api.avax.network/v1/apiUsageMetrics

Gets metrics for Glacier API usage over a specified time interval aggregated at the specified time-duration granularity.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Query Params

orgId

string

Organization ID to fetch usage metrics for

startTimestamp

integer

≥ 0

Query param for retrieving items after a specific timestamp.

endTimestamp

integer

≥ 0

Query param for retrieving items before a specific timestamp.

timeInterval

string

enum

Time interval granularity for data aggregation

Allowed:

groupBy

string

enum

Query param for the criterion used for grouping metrics

Allowed:

requestPath

string

Filter data by request path.

requestType

string

enum

Filter data by request type.

Allowed:

responseStatusCode

string

Filter data by response status code.

chainId

string

Filter data by chain ID.

apiKeyId

string

Filter data by API key ID.

Responses

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successful response

400Bad requests generally mean the client has passed invalid or malformed parameters. Error messages in the response could help in evaluating the error.

401When a client attempts to access resources that require authorization credentials but the client lacks proper authentication in the request, the server responds with 401.

403When a client attempts to access resources with valid credentials but doesn't have the privilege to perform that action, the server responds with 403.

404The error is mostly returned when the client requests with either mistyped URL, or the passed resource is moved or deleted, or the resource doesn't exist.

429This error is returned when the client has sent too many, and has hit the rate limit.

500The error is a generic server side error that is returned for any uncaught and unexpected issues on the server side. This should be very rare, and you may reach out to us if the problem persists for a longer duration.

502This is an internal error indicating invalid response received by the client-facing proxy or gateway from the upstream server.

503The error is returned for certain routes on a particular Subnet. This indicates an internal problem with our Subnet node, and may not necessarily mean the Subnet is down or affected.