# What is an API Product?

***

On API.market, to sell an API it needs to be packaged as a **Product**.

A Product is how customers discover, understand, and subscribe to your APIs. Think of it as the storefront listing for your API.

### :dart: Core Concept

A Product is composed of:

* **API Source** - The actual API endpoint specification
* **One or more Pricing Plans** - Subscription tiers for customers

### :package: Product Components

#### API Source

The API Source is the OpenAPI specification that connects your APIs to API.market. API.market acts as an API gateway and makes your API available via a unified API Gateway.

{% hint style="info" %}
:bulb: **How it works:** API.market makes it extremely easy for API developers to discover and integrate your API with a unified API platform. Your API is proxied through API.market, which handles authentication, billing, analytics, and more.
{% endhint %}

<figure><img src="/files/0o2DmDhqQ9U0QunFrP9R" alt=""><figcaption><p>How API.market works?</p></figcaption></figure>

***

#### Product Structure

Each API Product must have:

:white\_check\_mark: **One API Source** - The OpenAPI specification\
:white\_check\_mark: **One or more Pricing Plans** - Subscription options for customers

:point\_right: **Learn more:** [What is a Pricing Plan](/seller-docs/what-is-a-pricing-plan.md)

### :arrows\_counterclockwise: How Products Work

#### Subscription Model

A user can subscribe to **only one Pricing Plan** from a given Product. Users can upgrade or downgrade between Pricing Plans within the same product.

**Example Pricing Plans:**

* **Free** - $0/month
* **Pro** - $9/month
* **Ultra** - $49/month
* **Mega** - $199/month

{% hint style="warning" %}
:warning: **Important:** Users can only subscribe to one plan at a time, but they can upgrade or downgrade between plans as needed.
{% endhint %}

#### Public vs Private Products

API Sellers can use **private products** to offer custom pricing plans to specific users or organizations.

**Use cases for private products:**

* Enterprise customers with custom pricing
* Special promotional offers
* Beta testing programs
* Partner integrations

### :gear: Product Settings

You can edit all Product settings on the **Product Settings** page in your organization dashboard.

**Key settings include:**

* Product title and descriptions
* API Source configuration
* Pricing Plans management
* Product categories
* Documentation and examples
* Status (Draft/Published)

**Example of Product Setting Page**<br>

<figure><img src="/files/Xq07xrttqpmPoSfEWkA8" alt=""><figcaption></figcaption></figure>

#### Product Categories

Each Product can have a **maximum of three categories**. These categories are used to list your product on api.market.

{% hint style="success" %}
:white\_check\_mark: **Don't forget:** Click **Published** when you're done setting up your product to make it live on the marketplace!
{% endhint %}

**Category selection tips:**

* Choose categories that best describe your API's functionality
* Use specific categories to help customers find your API
* Categories help with search and discovery on API.market

<figure><img src="/files/y8EWc4x1WNyPf1HlslTe" alt=""><figcaption></figcaption></figure>

### :rocket: Next Steps

Now that you understand what an API Product is:

1. :point\_right: Import Your API Source - Connect your API
2. :point\_right: Create a Product using the Wizard - Build your product
3. :point\_right: What is a Pricing Plan - Set up pricing
4. :point\_right: Test Your APIs & Products - Verify everything works


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.api.market/seller-docs/what-is-an-api-product.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.