Skip to main content
API keys provide read-only access to published Metabind content for your client applications. 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 the x-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.

iOS Integration

Android Integration

React Integration

Best Practices

  1. Store keys securely: Never commit API keys to source control. Use environment variables or secure key management.
  2. Use separate keys per platform: Create dedicated keys for iOS, Android, and web applications for better tracking and security.
  3. Monitor usage: Check the lastUsed field to identify unused keys that can be revoked.
  4. Rotate keys periodically: Create new keys and migrate applications before revoking old ones.
  5. Handle errors gracefully: API keys can be revoked at any time. Implement proper error handling for 401 responses.