Authentication guide

  1. 1.Obtain your API key from the Wubble dashboard (Settings > Developer > API Keys)
  2. 2.Include the API key in the Authorization header of every request
  3. 3.Use the format: "Authorization: Bearer YOUR_API_KEY"
  4. 4.Ensure your API key is kept secure and never exposed in client-side code
  5. 5.Monitor your API usage in the dashboard to detect unauthorized access
  6. 6.Rotate your API keys regularly for enhanced security
  7. 7.Use separate API keys for development, staging, and production environments

Learn how to securely authenticate your API requests using Bearer token authentication. All requests to the Wubble API must include a valid API key in the Authorization header.

Notes

  • API keys should only be used in server-side code or secure environments. Never include them in client-side JavaScript, mobile apps, or version control systems.
  • If you receive a 401 Unauthorized error, check that your API key is valid, not revoked, and properly formatted in the Authorization header.
  • Store API keys in environment variables or secrets management systems like AWS Secrets Manager, HashiCorp Vault, or Azure Key Vault.

How would you rate the help you received from this article?

People also viewed

Generate your API key

Create and manage API keys for authenticating your requests

Error handling

Handle API errors gracefully with proper error codes

Rate limits and quotas

Understand API rate limits and how to handle throttling

Quick start guide

Make your first API call in minutes with step-by-step instructions

Still need help?

Can't find what you're looking for? Our team is here to help you get the most out of Wubble.

?