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

# SlapFive API

SlapFive API for customer advocacy platform. Manage boards, stories, members, companies, activities, requests, campaigns, content shares, content views, prompts, and AI assistant. The API exposes 31 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create or update board, get all boards. Covers 31 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create or update Board
- Get all Boards
- Delete Board
- Query and filter SlapFive API records by parameters
- Monitor SlapFive API operational status and events

## Use cases

### Marketing Operations

Use the SlapFive API to perform marketing operations programmatically. The API provides 31 endpoints covering core functionality including create or update board, get all boards, get specific board and its stories.

Example prompt: Call POST `/api/boards`/ to create or update board

### Automated AI Management

Automate ai operations by combining multiple SlapFive API endpoints. Agents can get all boards and then get specific board and its stories in a single workflow.

Example prompt: Call GET `/api/boards`/ to get all boards, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SlapFive 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 'create or update board', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/boards/` | Create or update Board |
| GET | `/api/boards/` | Get all Boards |
| GET | `/api/boards/{boardId}` | Get specific Board and its Stories |
| DELETE | `/api/boards/{boardId}` | Delete Board |
| POST | `/api/stories/` | Create or update Story |
| GET | `/api/stories/` | Get all Stories |
| GET | `/api/stories/{storyId}` | Get specific Story |
| DELETE | `/api/stories/{storyId}` | Delete Story |

## Key resources

- **AI** — Operations related to AI
- **Boards** — Operations related to Boards
- **Companies** — Operations related to Companies
- **Content** — Operations related to Content
- **Members** — Operations related to Members

## 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:** 59 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 54 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 65 / 100
- **View full report:** https://jentic.com/apis/slapfive.com/slapfive/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 SlapFive API by hand means sending your key in the api-authorization header to your own {company}.slapfive.com subdomain and managing the boards and stories calls yourself. Through Jentic you install once, import SlapFive from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** SlapFive puts the board id and story id in the URL path (`/api/boards/{boardId}` and `/api/stories/{storyId}`), so a rule can pin your agent to a specific board or story. You choose the operations it may call, so destructive ones like board deletion or story deletion are not included unless you add them.
- **Credential handling:** Your SlapFive 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 customer stories' or 'create a board', and Jentic returns the matching SlapFive 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 SlapFive API use?

The SlapFive API uses an API key passed in the `api-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 create or update board with the SlapFive API?

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

### What are the rate limits for the SlapFive 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 create or update board through Jentic?

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

### How many endpoints does the SlapFive API have?

The SlapFive API exposes 31 endpoints covering ai, boards, companies operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SlapFive operations and credentials the agent may use, and it can only call the endpoints you explicitly allow. SlapFive puts the board id and story id in the URL path (`/api/boards/{boardId}` and `/api/stories/{storyId}`), so a rule can pin the agent to a specific board or story. Destructive operations such as board deletion or story deletion stay out of scope unless you deliberately add them.