Skip to main content

Organization API Keys

Organization API keys let you authenticate at the organization scope. They are ideal for automation, service-to-service integrations, and workflows that need access across multiple projects in the same organization.

What they can do​

  • Access data and resources across all projects in the organization (subject to the key's permissions)
  • Perform organization-level actions such as creating, updating, listing, and deleting projects
  • Invoke project-scoped APIs by specifying the target project
caution

Treat organization keys like production secrets. They have broader access than project keys. Store them securely and rotate regularly.

Create an Organization API Key​

org-api-keys

  1. Go to the "Settings" page -> "API keys" section
  2. Click "Create Key"
caution

Copy the key once. For security reasons it cannot be shown again.

Use the key​

Include your key in the Authorization header:

Authorization: Bearer ORG_API_KEY

Example: list projects in the org​

curl -sS \
  -H "Authorization: Bearer $ORG_API_KEY" \
  https://api.getwren.ai/cloud/v1/projects?orgId={orgId}

Refer to the API Reference for full request/response schemas and additional parameters.

When to use org vs project keys​

  • Use an organization key for cross-project automation, provisioning, or admin tasks
  • Use a project key for application integrations that should be isolated to a single project

See also: Project API Keys and API Keys Overview