Staking Data

Error Codes

Common API error codes and their resolutions.

Error Codes

When making a request to our API, there may be times when an error is returned. If you are unable to resolve the issue, please contact us via Support Chat.

Not Authorized (401)

Message: you should be authenticated to do this request

Resolution: Requires valid X-API-KEY header authentication. Check for token expiration or permission issues.

User Not Found (401)

Message: user not found

Resolution: Invalid or unknown API key. Check account status via Support Chat.

Missing Limit Parameter (400)

Message: unable to parse paging argument: limit field is required

Resolution: The limit parameter is mandatory for list-returning queries.

Exceeding Maximum Limit (400)

Message: unable to parse paging argument: max limit is 500

Resolution: The limit parameter cannot exceed 500.

Invalid Argument (GRAPHQL_VALIDATION_FAILED)

Example: Typo detection like "metricss" vs "metrics"

Resolution: Check the suggestions provided for correct field names.

Variable Type Mismatch (GRAPHQL_VALIDATION_FAILED)

Example: Int cannot represent non-integer value: "1"

Resolution: Variables must match expected argument types.

Maximum Query Depth Exceeded (400)

Message: query path is too long. Max depth is 2

Resolution: Nested fields are limited to 2 levels.

Operation Not Found

Message: operation not found

Resolution: Occurs when request body lacks a valid query.

Field Conflict (GRAPHQL_VALIDATION_FAILED)

Description: Multiple fields with identical names but different arguments.

Resolution: Use aliases to differentiate fields with the same name.

{
  assets(where: { symbols: ["ETH"] }, limit: 1) {
    rewardRate: metrics(where: { metricKeys: ["reward_rate"] }, limit: 1) {
      defaultValue
    }
    price: metrics(where: { metricKeys: ["price"] }, limit: 1) {
      defaultValue
    }
  }
}

If you encounter an error not listed here, please contact Support Chat with the full error message and your query.

On this page