Skip to main content

Overview

Represents an API key that can be used to authenticate requests to the UGC Inc API. API keys are scoped to your organization and can be managed through the organization endpoints.

Fields

The actual API key value is only returned when the key is first created. For security reasons, it cannot be retrieved later. If you lose an API key, you’ll need to create a new one.

Key Management

Naming Best Practices

Give your API keys descriptive names to help you identify their purpose:
  • Environment-based: "Production API Key", "Development Key", "Staging Environment"
  • Service-based: "Backend Service Key", "Mobile App Key", "Analytics Dashboard"
  • Team-based: "Marketing Team Key", "Engineering Key", "Partner Integration"

Security Recommendations

  • Never commit API keys to version control
  • Store keys securely using environment variables or secrets managers
  • Rotate keys regularly
  • Delete unused keys immediately
  • Use separate keys for different environments (dev, staging, production)

Example Use Cases

Example Response

Authentication

To use an API key, include it in the Authorization header of your requests:
All API endpoints (except admin endpoints) require a valid API key for authentication.