read:content, rather than an unscoped key from Studio. See Scopes. This guide covers common usage patterns.
For the complete list of endpoints available with API key authentication, see Client API Endpoints.
Authentication Header
Include the API key in thex-api-key header for all requests:
Discovering Available Tags
Tags help categorize content and enable filtering in your application.Executing Saved Searches
Saved searches provide pre-configured queries that return consistent results.Fetching Content Types
Understand the content structure before rendering.Fetching Resolved Content
Get content with all dependencies resolved for rendering.Subscribing to Real-time Updates
Receive notifications when published content changes through the GraphQLcontentUpdated subscription, served over WebSocket at wss://ws-api.metabind.ai. See Subscriptions Overview for client setup.
iOS Integration
Android Integration
React Integration
Best Practices
- Store keys securely: Never commit API keys to source control. Use environment variables or secure key management.
- Use separate keys per platform: Create dedicated keys for iOS, Android, and web applications for better tracking and security.
-
Monitor usage: Check the
lastUsedfield to identify unused keys that can be revoked. - Rotate keys periodically: Create new keys and migrate applications before revoking old ones.
- Handle errors gracefully: API keys can be revoked at any time. Implement proper error handling for 401 responses.