Management API Overview

The Texture Management API gives you full programmatic control over your organization's configuration. Everything you can do in the Texture Dashboard — creating workspaces, managing team members, rotating API keys, configuring webhook destinations — you can automate through this API.

What you can automate#

Whether you're building a Terraform provider, a CI/CD pipeline, or a multi-tenant platform on top of Texture, the Management API is your foundation.

Getting started#

1. Create a Management API key#

1. Sign in to app.texturehq.com.
2. Navigate to Developer → API Keys.
3. Click Create API Key and select type MANAGEMENT.
4. Give it a descriptive name (e.g., "CI/CD Management Key").

You can view and manage your keys at any time from the Developer section of the Dashboard.

2. Make your first request#

curl -s https://api.texturehq.com/v1/workspaces \
  -H "Texture-Api-Key: management_abc123..."

import requests
 
resp = requests.get(
    "https://api.texturehq.com/v1/workspaces",
    headers={"Texture-Api-Key": "management_abc123..."}
)
print(resp.json())

const resp = await fetch("https://api.texturehq.com/v1/workspaces", {
  headers: { "Texture-Api-Key": "management_abc123..." },
});
const data = await resp.json();
console.log(data);

Authentication#

Management API keys use the same Texture-Api-Key header as other Texture API keys. See API Keys for details on creating and managing keys.

Management keys are scoped to your organization and can access all workspaces within it. They inherit the permissions of the user who created them — actions performed via the API are equivalent to the owner performing them in the Dashboard. For example, a non-admin user cannot use their management key to escalate their own role.

If you use a non-management key type (SERVER, API, etc.), management endpoints return:

{
  "message": "This endpoint requires a Management API key. Create one in your Dashboard under Developer → API Keys."
}

Rate limits#

Rate limits are enforced per API key using a sliding-window algorithm.

Response headers#

Every response includes rate-limit headers:

Pagination#

List endpoints use offset-based pagination:

Response metadata:

{
  "data": [...],
  "meta": {
    "total": 42,
    "page": 1,
    "perPage": 20
  }
}

Error handling#

Error responses include a message field, and may include a details object for validation errors:

{
  "message": "Invalid parameters provided.",
  "details": {
    "error": "The 'name' field is required."
  }
}

The API uses standard HTTP status codes. A few worth noting:

API versioning#

The Management API is currently at v1 (/v1/). We follow these principles:

• No breaking changes within a version. New fields may be added to responses, but existing fields won't be removed or change type.
• Deprecation notices will be communicated at least 90 days before any endpoint is retired.
• Additive changes (new endpoints, new optional parameters, new response fields) are shipped without a version bump.

Glossary#