x-glacier-api-key
header of your HTTP request.
An example curl request can be found below:
ratelimit-policy
- The rate limit policy tied to your api key.ratelimit-limit
- The number of requests you can send according to your policy.ratelimit-remaining
- How many request remaining you can send in the period for your policyratelimit-reset
retry-after
Both of these headers are set to the number of seconds until your period is over and requests will start succeeding again.2XX
range signifies successful requests, while those within the 4XX
range points to errors originating from the client’s side. Meanwhile, response codes within the 5XX
range indicates problems on the server’s side.
2XX
range signifies successful requests, while those within the 4XX
range points to errors originating from the client’s side. Meanwhile, response codes within the 5XX
range indicates problems on the server’s side.
The error response body is formatted like this:
Error Code | Error Type | Description |
---|---|---|
400 | Bad Request | Bad requests generally mean the client has passed invalid or malformed parameters. Error messages in the response could help in evaluating the error. |
401 | Unauthorized | When a client attempts to access resources that require authorization credentials but the client lacks proper authentication in the request, the server responds with 401. |
403 | Forbidden | When a client attempts to access resources with valid credentials but doesn’t have the privilege to perform that action, the server responds with 403. |
404 | Not Found | The 404 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. |
500 | Internal Server Error | The 500 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. |
502 | Bad Gateway | This is an internal error indicating invalid response received by the client-facing proxy or gateway from the upstream server. |
503 | Service Unavailable | The 503 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. |
5XX
range for a longer duration. These errors should be very rare, but we try to fix them as soon as possible once detected.pageSize
number of elements as passed in the request. Users can navigate to subsequent pages using the page token received in the nextPageToken
field. This method ensures efficient retrieval.
Routes with pagination have a following common response format: