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

# Showpad Sales Enablement API

Showpad API for managing content, users, channels, and sales enablement activities. The API exposes 7 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically list assets, get asset. Covers 7 operations with oauth2 authentication.

## Scope

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

## Capabilities

- List assets
- Get asset
- Integrate Showpad Sales Enablement API into automated workflows
- Query and filter Showpad Sales Enablement API records by parameters
- Monitor Showpad Sales Enablement API operational status and events

## Use cases

### Developer Tools Operations

Use the Showpad Sales Enablement API to perform developer tools operations programmatically. The API provides 7 endpoints covering core functionality including list assets, get asset, list channels.

Example prompt: Call GET /assets to list assets

### Automated Channels Management

Automate channels operations by combining multiple Showpad Sales Enablement API endpoints. Agents can get asset and then list channels in a single workflow.

Example prompt: Call GET `/assets/{asset_id}` to get asset, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Showpad Sales Enablement 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 oauth2 tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/assets` | List assets |
| GET | `/assets/{asset_id}` | Get asset |
| GET | `/channels` | List channels |
| GET | `/users` | List users |
| GET | `/users/{user_id}` | Get user |
| GET | `/divisions` | List divisions |
| GET | `/tags` | List tags |

## Key resources

- **Channels** — Operations related to Channels
- **Content** — Operations related to Content
- **Organization** — Operations related to Organization
- **Users** — Operations related to Users

## 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:** 70 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 90 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/showpad.com/showpad/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 Showpad Sales Enablement API by hand means running its OAuth2 flow, building the {subdomain}.showpad.com host for your account, and parsing its asset, channel, and user responses yourself. Through Jentic you install once, import the Showpad Sales Enablement API from the API Directory, store the OAuth credentials once, and your agent calls it.
- **Permission scoping:** The Showpad endpoints in this spec are all read-only lookups over assets, channels, users, divisions, and tags, so you limit the agent to the operations it needs, such as listing assets or fetching a user by id, and it can call nothing beyond the read operations you choose.
- **Credential handling:** Your Showpad OAuth 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 'list assets' or 'get a user by id', and Jentic returns the matching Showpad 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 Showpad Sales Enablement API use?

The Showpad Sales Enablement API uses OAuth 2.0 for authorization. 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 assets with the Showpad Sales Enablement API?

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

### What are the rate limits for the Showpad Sales Enablement 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 assets through Jentic?

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

### How many endpoints does the Showpad Sales Enablement API have?

The Showpad Sales Enablement API exposes 7 endpoints covering channels, content, organization operations.

### Can I limit what my agent is allowed to do with the Showpad Sales Enablement API?

Yes. Because Jentic One is self-hosted, you set the rules for which Showpad operations your agent may call and which OAuth credentials it may use. Every operation in this spec is a read-only lookup, so you can grant just the calls the agent needs, such as listing assets or fetching a user by id, and withhold the rest like listing channels, divisions, or tags. The agent can call nothing beyond the read operations you allow.