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

# Taggbox Widget API

Taggbox Widget API for retrieving gallery, feed, and post information from social media aggregation widgets. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get gallery information, get feed information for a gallery. Covers 3 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get gallery information
- Manage social media data programmatically
- Integrate Taggbox Widget API into automated workflows
- Query and filter Taggbox Widget API records by parameters
- Monitor Taggbox Widget API operational status and events

## Use cases

### Social Media Operations

Use the Taggbox Widget API to perform social media operations programmatically. The API provides 3 endpoints covering core functionality including get gallery information, get feed information for a gallery, get posts for a gallery.

Example prompt: Call GET /galleries to get gallery information

### Automated Feeds Management

Automate feeds operations by combining multiple Taggbox Widget API endpoints. Agents can get feed information for a gallery and then get posts for a gallery in a single workflow.

Example prompt: Call GET /feeds to get feed information for a gallery, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Taggbox Widget 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 'get gallery information', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/galleries` | Get gallery information |
| GET | `/feeds` | Get feed information for a gallery |
| GET | `/posts` | Get posts for a gallery |

## Key resources

- **Feeds** — Operations related to Feeds
- **Galleries** — Operations related to Galleries
- **Posts** — Operations related to Posts

## 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:** 45 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 50 / 100
- **View full report:** https://jentic.com/apis/taggbox.com/taggbox/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 Taggbox Widget API by hand means appending your user_key to the query string on every request and paging through galleries, feeds, and posts yourself. Through Jentic you install once, import the Taggbox Widget API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Taggbox's read calls pass their gallery target as a query parameter rather than a path resource, so limit the agent to the operations it needs, such as listing galleries or feeds, rather than to any one gallery. Every operation the agent can run is one you chose to allow.
- **Credential handling:** Your Taggbox user 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 'get gallery information' or 'list social feeds', and Jentic returns the matching Taggbox operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the Taggbox Widget API use?

The Taggbox Widget API uses an API key passed in the `user_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 get gallery information with the Taggbox Widget API?

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

### What are the rate limits for the Taggbox Widget 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 get gallery information through Jentic?

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

### How many endpoints does the Taggbox Widget API have?

The Taggbox Widget API exposes 3 endpoints covering feeds, galleries, posts operations.

### Can I limit what my agent is allowed to do with the Taggbox Widget API?

Yes. Because you run Jentic One yourself, your own rules decide which Taggbox operations and credentials the agent may use. The Taggbox Widget API exposes three read calls, GET /galleries, GET /feeds, and GET /posts, that take their gallery target as a query parameter rather than a path resource, so you scope the agent by allowing only the operations it needs, such as listing galleries or feeds. Every operation the agent can run is one you chose to allow.