canonical: https://jentic.com/apis/blue.cc/blue

# Blue Cc Blue REST API

The Blue REST API manages work across workspaces, lists, records, and custom databases. It creates records, moves them between lists, searches and counts them, and tracks their comments, activity, and field history. Beyond individual records it builds dashboards, charts, and reports over record data, configures custom fields and typed database fields, runs automations with triggers and actions, and handles file uploads through a presigned flow. Every operation is available as an RPC call, and core resources also expose resource-style routes.

## For AI agents

Manage Blue work: create, move, and search records across workspaces and lists, add comments, configure databases and custom fields, build reports and charts, run automations, and upload files.

## Scope

Does not handle billing, time tracking, or video calls. Use for managing records, workspaces, databases, and reports in Blue only.

## Capabilities

- Create records, move them between lists, and search or count them in a workspace
- Organise work into workspaces, lists, and custom databases with typed fields
- Add comments to records and read their activity and field history
- Build dashboards, charts, and reports over record data
- Run automations with triggers and actions on a database
- Upload files to records through a presigned upload flow
- Invite users to a workspace and manage their roles and assignments

## Use cases

### Agent Record Management

An AI agent connected through Jentic keeps a Blue workspace tidy: it creates records from incoming requests, searches for duplicates before adding one, moves records between lists as their status changes, and adds a comment summarising what it did. Every operation is available as a single RPC call, so the agent chains them without learning resource-route conventions.

Example prompt: Search a workspace for an existing record, create one if none matches, move it to the 'In progress' list, and add a comment

### Reporting and Dashboards

An operations team turns Blue records into live reporting by building charts on a dashboard and aggregating report data over a field. The Blue REST API exposes report, chart, and dashboard operations plus metric series, so an agent can assemble a status view without exporting data to a separate BI tool.

Example prompt: Create a chart on a dashboard from a database's records and aggregate a report over a chosen field

### Database Automation

A team removes manual steps by configuring custom database fields and wiring an automation with a trigger and actions. When a record changes, Blue runs the automation, and the API also manages the fields, options, and views the automation depends on. An agent can set this up end to end from the field configuration through the automation.

Example prompt: Create a database field, then create an automation that fires when that field changes and performs an action

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/list-workspaces` | List workspaces |
| POST | `/create-record` | Create a record |
| POST | `/search-records` | Search records in a workspace |
| POST | `/move-record` | Move a record to another list |
| POST | `/add-comment` | Add a comment to a record |
| POST | `/aggregate-report` | Aggregate a report over a field |
| POST | `/create-automation` | Create an automation |
| POST | `/list-databases` | List databases in a workspace |

## Key resources

- **Records** — Create, update, move, search, count, archive, and duplicate records
- **Workspaces and lists** — Create and manage workspaces, lists, tags, and members
- **Databases** — Configure databases, typed fields, field options, and records
- **Reports and dashboards** — Build reports, charts, dashboards, and metric series over record data
- **Automations** — Create and manage triggers and actions on a database
- **Files** — Upload files to records through a presigned flow

## 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:** 60 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 77 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 78 / 100
  - Security: 60 / 100
  - AI Discoverability: 69 / 100
- **View full report:** https://jentic.com/apis/blue.cc/blue/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 Blue REST API by hand means managing a Personal Access Token, sending the `blue-org-id` scope header on every call, and learning both the RPC and resource-style routes plus the presigned upload flow. Through Jentic you install once, import the Blue REST API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Blue offers every operation as an RPC call that carries the workspace and record ids in the request body, so a rule bounds which operations your agent may call, not which workspace. You choose the operations it may call, so destructive ones like delete-record, remove-workspace-member, and manage-automation are not included unless you add them.
- **Credential handling:** Your Blue Personal Access 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 'create a record' or 'search a workspace', and Jentic returns the matching Blue operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Asana is a work-management platform with tasks, projects, and custom fields, overlapping with Blue.
- **ClickUp** — ClickUp manages tasks, docs, and dashboards, a comparable work surface to Blue.
- **Notion** — Notion stores docs and databases that can mirror or document the records Blue tracks.

## FAQ

### What authentication does the Blue REST API use?

The Blue REST API authenticates with a bearer Personal Access Token in the Authorization header, and requests are scoped with the `blue-org-id` header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt, logs, or context.

### Can I search and move records with the Blue REST API?

Yes. You can search records within a workspace, count them, create and update them, and move a record between lists. Each is available as a single RPC call, so an agent can find a record, reposition it, and comment on it in sequence.

### What are the rate limits for the Blue REST API?

The OpenAPI spec does not specify numeric rate limits for the Blue REST API. Check https://blue.cc for the current limits that apply to your plan before running bulk record or report operations.

### Is there a Blue MCP server?

You don't need an MCP server to give your agent the Blue REST API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls it. Operations are discovered on demand, so your agent's context stays lean instead of loading a separate server's tool definitions.

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

Yes. Write a rule that allows only the read operations, such as listing and searching records and reading reports, and leave out destructive ones like delete-record, remove-workspace-member, and manage-automation. The agent can then report on a workspace without changing it, and every call it makes is logged.

### How do I create a record through Jentic?

Import the Blue REST API from the Jentic API Directory, store your Personal Access Token once, and have your agent search Jentic for 'create a record'. Jentic returns the create-record operation with its input schema so the agent sends the `workspaceId` and `title` and reads back the new record. To run it on your own infrastructure, install Jentic One from its GitHub repo.