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

# VivifyScrum API

Project management and Scrum tool API. Manage tasks/items, sprints, and boards. The API exposes 8 endpoints secured with bearer authentication.

## For AI agents

Programmatically add a new item/task, edit an item. Covers 8 operations with bearer authentication.

## Scope

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

## Capabilities

- Add a new item/task
- Edit an item
- Delete an item
- Get item by code or ID
- List sprints
- Export sprint data

## Use cases

### Productivity Operations

Use the VivifyScrum API to perform productivity operations programmatically. The API provides 8 endpoints covering core functionality including add a new item/task, edit an item, delete an item.

Example prompt: Call POST /task to add a new item/task

### Automated Board Export Management

Automate board export operations by combining multiple VivifyScrum API endpoints. Agents can edit an item and then delete an item in a single workflow.

Example prompt: Call PUT /task to edit an item, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call VivifyScrum 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 'add a new item/task', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/task` | Add a new item/task |
| PUT | `/task` | Edit an item |
| DELETE | `/task` | Delete an item |
| GET | `/task/{taskCode}` | Get item by code or ID |
| GET | `/sprints` | List sprints |
| GET | `/sprints/{sprintId}/tasks` | Get sprint items |
| GET | `/sprints/{sprintId}/export` | Export sprint data |
| GET | `/board-export` | Export board (once per 24h) |

## Key resources

- **Board Export** — Operations for board export
- **Sprints** — Operations for sprints
- **Task** — Operations for task

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/vivifyscrum.com/vivifyscrum/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 VivifyScrum by hand means handling its bearer token auth against www.vivifyscrum.com and managing the task and sprint calls yourself. Through Jentic you install once, import VivifyScrum from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** VivifyScrum puts the sprint id in the URL path (`/sprints/{sprintId}/tasks`), so a rule can pin your agent to reading and exporting one sprint. You choose the operations it may call, so task deletion on /task is not included unless you add it.
- **Credential handling:** Your VivifyScrum bearer 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 'add a new task' or 'list tasks in a sprint', and Jentic returns the matching VivifyScrum 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 VivifyScrum API use?

The VivifyScrum 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 add a new item/task with the VivifyScrum API?

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

### What are the rate limits for the VivifyScrum 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 add a new item/task through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add a new item/task'. Jentic returns the matching VivifyScrum API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The VivifyScrum API exposes 8 endpoints covering board export, sprints, task operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which VivifyScrum operations and credentials your agent may use. Because the sprint id sits in the URL path, such as GET `/sprints/{sprintId}/tasks` and GET `/sprints/{sprintId}/export`, you can pin the agent to reading and exporting a single sprint. You also choose which operations it can call, so a destructive request like DELETE /task is off limits unless you explicitly add it.