canonical: https://jentic.com/apis/stubhub.ie/stubhub-ie

# Stubhub Ie StubHub Seller API

StubHub API for sellers to manage ticket listings, handle webhooks for inventory and sales events, and authenticate via OAuth. The API exposes 3 endpoints secured with basic, bearer authentication.

## For AI agents

Programmatically generate access token, register webhook subscription. Covers 3 operations with basic, bearer authentication.

## Scope

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

## Capabilities

- Generate access token
- Register webhook subscription
- Create ticket listing
- Query and filter StubHub Seller API records by parameters
- Monitor StubHub Seller API operational status and events

## Use cases

### Developer Tools Operations

Use the StubHub Seller API to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including generate access token, register webhook subscription, create ticket listing.

Example prompt: Call POST /sellers/oauth/accesstoken to generate access token

### Automated Authentication Management

Automate authentication operations by combining multiple StubHub Seller API endpoints. Agents can register webhook subscription and then create ticket listing in a single workflow.

Example prompt: Call POST /partners/webhooks/v3 to register webhook subscription, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call StubHub 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 basic, bearer tokens manually.

Example prompt: Search Jentic for 'generate access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /sellers/oauth/accesstoken | Generate access token |
| POST | /partners/webhooks/v3 | Register webhook subscription |
| POST | /sellers/inventory/listings/v3 | Create ticket listing |

## Key resources

- **Authentication** — OAuth token generation
- **Webhooks** — Webhook subscription management
- **Listings** — Ticket listing management

## Why Jentic

- **Setup:** Wiring the StubHub Seller API by hand means exchanging your consumer key and secret for an access token, then switching between basic and bearer auth per request yourself. Through Jentic you install once, import the StubHub Seller API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** StubHub Seller operations carry their targets in the request body, so you limit the agent to the operations it needs, such as generating an access token or creating an inventory listing. Because you choose the operations, registering a partner webhook is not available unless you include it in the allowed set.
- **Credential handling:** Your StubHub Seller credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'generate an access token' or 'create an inventory listing', and Jentic returns the matching StubHub Seller 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 StubHub Seller API use?

The StubHub Seller API uses basic, bearer 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 generate access token with the StubHub Seller API?

Yes. Use the POST /sellers/oauth/accesstoken endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the StubHub 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 generate access token through Jentic?

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

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

The StubHub Seller API exposes 3 endpoints covering authentication, webhooks, listings operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which StubHub Seller operations and credentials the agent may use. Because each operation carries its target in the request body, you can allow only what the agent needs, such as generating an access token or creating an inventory listing, while leaving registering a partner webhook out of the allowed set. The agent can call only the operations you permit, and your stored credentials are injected at execution time rather than exposed in the agent context.