> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fabricgateway.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fabricgateway.ai/_mcp/server.

# Admin API reference

> Find the base URL, authentication, and resources of the Fabric AI Gateway admin API, which you use to configure your organization from scripts and agents.

The admin API configures your organization: its connections, routes, plugin instances, and more. It's a JSON REST API on the control plane, and a change that you make through it reaches your data planes the same way a console change does. The gateway API is different: your applications call it to send traffic. This page lists what the admin API offers. For the steps and examples, see [Configure the gateway with the admin API](/configure/automation/admin-api).

## Base URL

Every admin API path starts with your tenant ID:

```text
https://CONTROL_PLANE_HOST/api/v1/TENANT_ID/RESOURCE
```

To find your tenant ID, select your organization name at the bottom of the console sidebar, select **Account settings**, and copy **Tenant ID**. A request with any other tenant ID gets `403`.

Paths without a namespace act on the Default namespace, not on the namespace you've selected in the console. To work in another namespace, put `namespaces/NAMESPACE_ID` before the resource, for example `/api/v1/TENANT_ID/namespaces/NAMESPACE_ID/routes`. For details, see [Work in a namespace](/configure/automation/admin-api#work-in-a-namespace).

## Authentication

Send an API key in the `fg-tenant-api-key` header, and send JSON bodies with `Content-Type: application/json`. An API key acts for the whole organization. It can't manage API keys, including listing them. For the steps to create one, see [Manage API keys](/configure/automation/api-keys).

## Resources

| Resource               | Path                                          | Methods                                                          |
| ---------------------- | --------------------------------------------- | ---------------------------------------------------------------- |
| Services (connections) | `/services`, `/services/NAME`                 | `GET`, `POST`, `PUT`, `DELETE`                                   |
| Routes                 | `/routes`, `/routes/NAME`                     | `GET`, `POST`, `PUT`, `DELETE`                                   |
| Plugin instances       | `/plugin-instances`, `/plugin-instances/NAME` | `GET`, `POST`, `PUT`, `DELETE`                                   |
| Credentials            | `/credentials`, `/credentials/ID`             | `GET`, `POST`, `PATCH`, `DELETE`                                 |
| Namespaces             | `/namespaces`, `/namespaces/ID`               | `GET`, `POST`, `PATCH`, `DELETE`                                 |
| Budgets                | `/budgets`                                    | `GET`, `PUT`                                                     |
| Vaults                 | `/vaults`, `/vaults/NAME`                     | `GET`, `POST`, `PUT` (`POST` and `PUT` need your own data plane) |
| LLM token usage        | `/analytics/llm-usage`                        | `GET`                                                            |

`PUT` replaces the whole resource, so send every field, not only the ones you change.

A connection also accepts `POST /services/NAME/disable` and `POST /services/NAME/resume` to pause and restart it. A credential accepts `POST /credentials/ID/rotate` and `POST /credentials/ID/revoke`.

## Next steps

* [Configure the gateway with the admin API](/configure/automation/admin-api)
* [Manage API keys](/configure/automation/api-keys)
* [Understand credentials and keys](/concepts/credentials-and-keys)