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

# Redbooth API

Redbooth is a collaboration and project management platform. The API provides access to tasks, projects, conversations, files, notes, and more. The API exposes 29 endpoints secured with bearer authentication.

## For AI agents

Programmatically list activities, create a comment. Covers 29 operations with bearer authentication.

## Scope

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

## Capabilities

- List activities
- Create a comment
- Get a comment
- Update a comment
- Delete a comment

## Use cases

### Productivity Operations

Use the Redbooth API to perform productivity operations programmatically. The API provides 29 endpoints covering core functionality including list activities, create a comment, list comments.

Example prompt: Call GET /activities to list activities

### Automated Activities Management

Automate activities operations by combining multiple Redbooth API endpoints. Agents can create a comment and then list comments in a single workflow.

Example prompt: Call POST /comments to create a comment, then verify the result

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/activities` | List activities |
| POST | `/comments` | Create a comment |
| GET | `/comments` | List comments |
| GET | `/comment/{id}` | Get a comment |
| PUT | `/comment/{id}` | Update a comment |
| DELETE | `/comment/{id}` | Delete a comment |
| POST | `/conversations` | Create a conversation |
| GET | `/conversations` | List conversations |

## Key resources

- **Activities** — Operations related to Activities
- **Comments** — Operations related to Comments
- **Conversations** — Operations related to Conversations
- **Organizations** — Operations related to Organizations
- **Projects** — Operations related to Projects

## 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:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/redbooth.com/redbooth/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 Redbooth API by hand means handling its bearer token auth, pointing at the redbooth.com/api/3 host, and managing requests yourself. Through Jentic you install once, import the Redbooth API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Redbooth puts the comment id in the URL path (`/comment/{id}`), so a rule can pin your agent to specific comments alongside its activity and conversation lists. You choose the operations it may call, so writes like updating or deleting a comment are only included if you add them.
- **Credential handling:** Your Redbooth token 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 'post a comment' or 'list activities', and Jentic returns the matching Redbooth operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Redbooth API use?

The Redbooth API uses a Bearer token in the 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 list activities with the Redbooth API?

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

### What are the rate limits for the Redbooth 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 activities through Jentic?

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

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

The Redbooth API exposes 29 endpoints covering activities, comments, conversations operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Redbooth operations and credentials the agent can use, so it might only list activities and conversations while every other call stays off. Redbooth puts the comment id in the URL path at `/comment/{id}`, which lets a rule pin the agent to specific comments rather than the whole account. Write operations such as POST /comments, PUT `/comment/{id}`, and DELETE `/comment/{id}` are included only if you explicitly add them.