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

# Tradable Bits API

Fan engagement and CRM platform API. Manage fans, segments, tickets, performances, streams, and more. The API exposes 38 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list available segments, get segment metrics. Covers 38 operations with apiKey authentication.

## Scope

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

## Capabilities

- List available segments
- Get segment metrics
- Create fan record
- Search fan records
- Update fan

## Use cases

### Marketing Operations

Use the Tradable Bits API to perform marketing operations programmatically. The API provides 38 endpoints covering core functionality including list available segments, get segment metrics, get fans in a segment.

Example prompt: Call GET `/v1/segments` to list available segments

### Automated Apps Management

Automate apps operations by combining multiple Tradable Bits API endpoints. Agents can get segment metrics and then get fans in a segment in a single workflow.

Example prompt: Call GET `/v1/segments/{segment_type}/{segment_id}/status` to get segment metrics, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Tradable Bits 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 'list available segments', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/segments` | List available segments |
| GET | `/v1/segments/{segment_type}/{segment_id}/status` | Get segment metrics |
| GET | `/v1/segments/{segment_type}/{segment_id}` | Get fans in a segment |
| POST | `/v1/crm/fans` | Create fan record |
| GET | `/v1/crm/fans` | Search fan records |
| POST | `/v1/crm/fans/{fan_id}` | Update fan |
| GET | `/v1/crm/fans/{fan_id}` | Get specific fan |
| DELETE | `/v1/crm/fans/{fan_id}` | Delete fan |

## Key resources

- **Apps** — Operations related to Apps
- **CRM** — Operations related to CRM
- **Entertainment** — Operations related to Entertainment
- **Idols** — Operations related to Idols
- **Media** — Operations related to Media

## Why Jentic

- **Setup:** Wiring the Tradable Bits API by hand means appending its api_key query parameter to every call, tracking the tradablebits.com host, and coding your own request and pagination handling for fans and segments. Through Jentic you install once, import the Tradable Bits API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Tradable Bits puts the fan id in the URL path (`/v1/crm/fans/{fan_id}`), so a rule can pin your agent to a specific fan and the operations it needs there. You choose which operations it may call, so destructive ones like deleting a fan are not included unless you add them.
- **Credential handling:** Your Tradable Bits 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 'list available segments' or 'get a fan record', and Jentic returns the matching Tradable Bits operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the Tradable Bits API use?

The Tradable Bits API uses an API key passed in the `api_key` query. 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 list available segments with the Tradable Bits API?

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

### What are the rate limits for the Tradable Bits 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 list available segments through Jentic?

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

### How many endpoints does the Tradable Bits API have?

The Tradable Bits API exposes 38 endpoints covering apps, crm, entertainment operations.

### Can I limit what my agent is allowed to do with the Tradable Bits API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Tradable Bits operations and credentials the agent may use. Because the fan id sits in the URL path (`/v1/crm/fans/{fan_id}`), you can pin the agent to a specific fan and only the operations it needs there, such as reading or searching fan records. You choose which operations it may call, so a destructive action like deleting a fan (DELETE `/v1/crm/fans/{fan_id}`) is not available to the agent unless you explicitly add it.