canonical: https://jentic.com/apis/whatnot.com/whatnot

# Whatnot Seller API

The Whatnot Seller API is a GraphQL API for managing products and receiving notifications when items sell on the Whatnot marketplace. Note: This is a GraphQL API accessed via a single POST endpoint. The API exposes 1 endpoints secured with bearer authentication.

## For AI agents

Programmatically execute graphql query. Covers 1 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Execute GraphQL query
- Manage e commerce data programmatically
- Integrate Whatnot Seller API into automated workflows
- Query and filter Whatnot Seller API records by parameters
- Monitor Whatnot Seller API operational status and events

## Use cases

### E-Commerce Operations

Use the Whatnot Seller API to perform e commerce operations programmatically. The API provides 1 endpoints covering core functionality including execute graphql query.

Example prompt: Call POST `/seller-api/graphql` to execute graphql query

### Data Retrieval and Monitoring

Query Whatnot Seller API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Whatnot Seller API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Whatnot Seller 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 bearer tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/seller-api/graphql` | Execute GraphQL query |

## Key resources

- **GraphQL** — Operations related to GraphQL

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/whatnot.com/whatnot/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Whatnot Seller API by hand means placing its bearer token on the single GraphQL endpoint and handling retries yourself. Through Jentic you install once, import the Whatnot Seller API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Whatnot Seller API exposes one GraphQL operation and carries the query in the request body rather than in the path, so limit the agent to that operation. You choose the operations it may call, so nothing beyond the GraphQL endpoint runs unless you add it.
- **Credential handling:** Your Whatnot Seller API token 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 'run a seller GraphQL query', and Jentic returns the matching Whatnot Seller API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Whatnot Seller API use?

The Whatnot Seller API uses a Bearer token 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 execute graphql query with the Whatnot Seller API?

Yes. Use the POST `/seller-api/graphql` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Whatnot Seller 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 execute graphql query through Jentic?

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

### How many endpoints does the Whatnot Seller API have?

The Whatnot Seller API exposes 1 endpoints covering graphql operations.

### Can I limit what my agent is allowed to do with the Whatnot Seller API?

Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. The Whatnot Seller API exposes a single GraphQL operation at POST `/seller-api/graphql`, and you choose whether the agent may call it, so nothing beyond that endpoint runs unless you add it. Your bearer token stays with your instance and is injected only when the agent runs the operations you permit.