Grid implements a robust authentication system that combines API key authentication with blockchain-specific security features. This guide explains how to authenticate your requests and manage your API keys securely.

API Keys

Getting your API Keys

API Key Scoping

API keys in Grid are scoped in two ways:

  1. Feature Scope: Each API key is granted access to specific features and endpoints. If you need access to additional features, please contact Grid support.
  2. Environment Scope: API keys are tied to specific environments (production or sandbox). You’ll need separate API keys for each environment. For more details about environments, see the Environments guide.

Using API Keys

All API requests must include your API key in the Authorization header:

Authorization
string
required

Bearer token authentication. Format: Bearer <your-api-key>. The API key must be a valid UUID and must be active (not disabled).

API Key Security

  • Never commit API keys to version control
  • Use environment variables to store API keys
  • Use different API keys for development and production

Support

If you need access to additional features or have questions about API key scoping, please reach out to your Grid representative or reach out to us at grid[at]sqds.io.