canonical: https://jentic.com/apis/swaggerhub.ram.grandhi/wso2-api-manager---store

# Ram Grandhi WSO2 API Manager - Store

This specifies a **RESTful API** for WSO2 **API Manager** - Store. Please see [full swagger definition](https://raw.githubusercontent.com/wso2/carbon-apimgt/v6.0.4/components/apimgt/org.wso2.carbon.apimgt.rest.api.store/src/main/resources/store-api.yaml) of the API which is written using [swagger 2.0](http://swagger.io/) specification. The API exposes 21 endpoints.

## For AI agents

Programmatically retrieve/search apis
, generate sdk for an API
. Covers 21 operations.

## Scope

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

## Capabilities

- Retrieve/Search APIs
- Generate SDK for an API
- Get details of an API
- Query and filter WSO2 API Manager - Store records by parameters
- Monitor WSO2 API Manager - Store operational status and events

## Use cases

### Developer Tools Operations

Use the WSO2 API Manager - Store to perform developer tools operations programmatically. The API provides 21 endpoints covering core functionality including retrieve/search apis
, generate sdk for an API
, get details of an API
.

Example prompt: Call GET /apis to retrieve/search apis

### Automated Apis Management

Automate apis operations by combining multiple WSO2 API Manager - Store endpoints. Agents can generate sdk for an API
 and then get details of an API
 in a single workflow.

Example prompt: Call POST `/apis/generate-sdk`/ to generate sdk for an API
, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call WSO2 API Manager - Store 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 none tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/apis` | Retrieve/Search APIs |
| POST | `/apis/generate-sdk/` | Generate SDK for an API |
| GET | `/apis/{apiId}` | Get details of an API |
| GET | `/apis/{apiId}/documents` | Get a list of documents of an API |
| GET | `/apis/{apiId}/documents/{documentId}` | Get a document of an API |
| GET | `/apis/{apiId}/documents/{documentId}/content` | Get the content of an API document |
| GET | `/apis/{apiId}/swagger` | Get swagger definition |
| GET | `/apis/{apiId}/thumbnail` | Get thumbnail image |

## Key resources

- **Apis** — Operations for apis
- **Applications** — Operations for applications
- **Subscriptions** — Operations for subscriptions
- **Tags** — Operations for tags
- **Tiers** — Operations for tiers

## Why Jentic

- **Setup:** Wiring the WSO2 API Manager Store API by hand means pointing at its wso2.com store host, coding the API search and document-retrieval calls, and handling retries yourself even though it takes no credential here. Through Jentic you install once, import the WSO2 API Manager Store API from the API Directory, and your agent calls it.
- **Permission scoping:** This API puts the API id in the URL path (`/apis/{apiId}/...`), so a rule can pin your agent to one published API: it can read that API, its documents, and its swagger and nothing else. You choose the operations it may call, so SDK generation is not included unless you add it.
- **Credential handling:** The WSO2 API Manager Store API needs no credential in this spec, so there is nothing to store, and any host configuration is held by your own Jentic One instance and applied at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search published APIs' or 'read an API's documentation', and Jentic returns the matching WSO2 API Manager Store 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 WSO2 API Manager - Store use?

The WSO2 API Manager - Store uses no authentication. 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 retrieve/search apis
 with the WSO2 API Manager - Store?

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 WSO2 API Manager - Store?

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 retrieve/search apis
 through Jentic?

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

### How many endpoints does the WSO2 API Manager - Store have?

The WSO2 API Manager - Store exposes 21 endpoints covering apis, applications, subscriptions operations.

### Can I limit what my agent is allowed to do with the WSO2 API Manager - Store API?

Yes. Jentic One is self-hosted, so your own rules decide which WSO2 API Manager - Store operations the agent may call. Because the API puts the API id in the URL path (`/apis/{apiId}/...`), you can pin the agent to a single published API and let it only read that API, its documents, and its swagger definition. You choose the operations it is permitted to use, so SDK generation via POST `/apis/generate-sdk`/ is not available to the agent unless you explicitly add it.