canonical: https://jentic.com/apis/swaggerhub.com/swaggerhub-registry-api

# Com SwaggerHub Registry API

Overview Use SwaggerHub Registry API to access, manage, and update the following resources in SwaggerHub, bypassing the web interface: * APIs * Domains * Integrations * Projects * Templates SwaggerHub also provides the [User Management API](https://app.swaggerhub.com/apis-docs/swagger-hub/user-management-api/) to get information about organizations and manage organization members. Base URL Use the. The API exposes 87 endpoints secured with apiKey authentication.

## For AI agents

Programmatically search apis, get a list of apis of the specified owner. Covers 87 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Search APIs
- Get a list of APIs of the specified owner
- Create or update an API
- Delete an API
- Rename an API

## Use cases

### Developer Tools Operations

Use the SwaggerHub Registry API to perform developer tools operations programmatically. The API provides 87 endpoints covering core functionality including search apis, get a list of apis of the specified owner, create or update an API.

Example prompt: Call GET /apis to search apis

### Automated APIs Management

Automate apis operations by combining multiple SwaggerHub Registry API endpoints. Agents can get a list of apis of the specified owner and then create or update an API in a single workflow.

Example prompt: Call GET `/apis/{owner}` to get a list of apis of the specified owner, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SwaggerHub Registry API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'search apis', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/apis` | Search APIs |
| GET | `/apis/{owner}` | Get a list of APIs of the specified owner |
| POST | `/apis/{owner}/{api}` | Create or update an API |
| GET | `/apis/{owner}/{api}` | Get a list of API versions |
| DELETE | `/apis/{owner}/{api}` | Delete an API |
| POST | `/apis/{owner}/{api}/rename` | Rename an API |
| GET | `/apis/{owner}/{api}/settings/default` | Get the default version of an API |
| PUT | `/apis/{owner}/{api}/settings/default` | Set the default API version |

## Key resources

- **APIs** — Manage your API definitions
- **Templates** — Manage your API [custom templates](https://support.smartbear.com/swaggerhub/docs/apis/creating-api-c
- **Domains** — Manage your [domains](https://support.smartbear.com/swaggerhub/docs/domains/)
- **Projects** — Manage your organization's [projects](https://support.smartbear.com/swaggerhub/docs/organizations/pr
- **Integrations** — Create and configure [integrations](https://support.smartbear.com/swaggerhub/docs/integrations/) pro

## Why Jentic

- **Setup:** Wiring the SwaggerHub Registry API by hand means setting up its API key in the Authorization header, tracking the owner, API, and version path segments across dozens of endpoints, and handling responses yourself. Through Jentic you install once, import the SwaggerHub Registry API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Registry API puts the owner and API in the URL path (`/apis/{owner}/{api}/...`), so a rule can pin your agent to one owner or API: it can read and comment on that API and nothing else. You choose the operations it may call, so destructive ones like deleting an API or renaming it are not included unless you add them.
- **Credential handling:** Your SwaggerHub API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search APIs' or 'get an API definition', and Jentic returns the matching SwaggerHub Registry API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the SwaggerHub Registry API use?

The SwaggerHub Registry API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I search apis with the SwaggerHub Registry API?

Yes. Use the GET /apis endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SwaggerHub Registry API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I search apis through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search apis'. Jentic returns the matching SwaggerHub Registry API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SwaggerHub Registry API have?

The SwaggerHub Registry API exposes 87 endpoints covering apis, templates, domains operations.

### Can I limit what my agent is allowed to do with the SwaggerHub Registry API?

Yes. Because you run Jentic One yourself and it is self-hosted, your own rules decide which SwaggerHub operations and credentials the agent may use. Since the Registry API puts the owner and API in the URL path (`/apis/{owner}/{api}`), you can pin the agent to a single owner or API so it only reads and updates that one and nothing else. You also choose the exact operations it may call, so destructive ones like DELETE `/apis/{owner}/{api}` or POST `/apis/{owner}/{api}/rename` stay off unless you explicitly grant them.