canonical: https://jentic.com/apis/priorit.io/priorit

# Priorit Prioritio API

Jentic publishes the only available OpenAPI specification for Prioritio API, keeping it validated and agent-ready. Prioritio API provides task and priority management with 5 endpoints for creating, listing, retrieving, and updating tasks. Each task supports four priority levels (low, medium, high, critical) and three status stages (open, in_progress, completed), with due dates for deadline tracking. The API also exposes priority configuration data for customizing how tasks are categorized.

## For AI agents

Create, list, and update prioritized tasks with due dates and status tracking. Supports four priority levels and three workflow statuses for lightweight task management.

## Scope

Does not handle project hierarchies, team collaboration, time tracking, or file attachments - use for priority-based task creation and status tracking only.

## Capabilities

- Create tasks with title, description, priority level, and due date
- Filter task lists by status to focus on open or in-progress items
- Update task priority from low through critical as urgency changes
- Transition tasks through open, in_progress, and completed statuses
- Retrieve priority configurations including level names and color codes

## Use cases

### Priority-Based Task Triage

Use the Prioritio API to triage incoming work items by assigning priority levels from low to critical. Agents can list all open tasks filtered by status, identify items lacking a priority assignment, and batch-update priorities based on due date proximity or business rules. This is particularly useful for teams processing inbound requests where items need rapid categorization.

Example prompt: List all tasks with status 'open', identify any without a priority set, and update them to 'medium' priority

### Deadline Tracking and Status Updates

Track task deadlines and transition items through workflow stages as work progresses. The API stores due_date on each task and supports status values of open, in_progress, and completed. Agents can identify overdue tasks by comparing due_date against the current date and move completed work to the done state without manual intervention.

Example prompt: Retrieve all tasks with status 'in_progress', check which have a due_date before today, and update those overdue tasks to include 'OVERDUE' in their description

### AI Agent Task Management Integration

AI agents can use the Prioritio API through Jentic to manage task backlogs, create items from parsed emails or messages, and keep priority assignments aligned with business goals. Jentic provides the structured operation schemas and credential isolation so agents can call Prioritio endpoints without storing bearer tokens in their context.

Example prompt: Search Jentic for 'create a prioritized task', load the createTask operation schema, and execute it with title 'Review Q3 report', priority 'high', and due_date '2026-07-01'

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/tasks` | List tasks with status and pagination filters |
| POST | `/tasks` | Create a new task with priority and due date |
| GET | `/tasks/{id}` | Retrieve a specific task by ID |
| PUT | `/tasks/{id}` | Update task priority, status, or details |
| GET | `/priorities` | List priority level configurations |

## Key resources

- **Tasks** — Create, list, retrieve, and update tasks with priority levels, statuses, and due dates
- **Priorities** — Retrieve priority level configurations including names, levels, and color codes

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/priorit.io/priorit/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 Prioritio by hand means managing its bearer token, pointing calls at api.priorit.io/v1, and mapping task and priority operations yourself. Through Jentic you install once, import Prioritio from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Prioritio puts the task id in the URL path (`/tasks/{id}`), so a rule can pin your agent to reading and updating specific tasks. You choose the operations it may call, so creating or overwriting a task is not included unless you add it.
- **Credential handling:** Your Prioritio 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 'create a high-priority task' or 'list overdue tasks', and Jentic returns the matching Prioritio operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana API** — Full-featured project management with teams, projects, and subtasks vs Prioritio's lightweight task prioritization
- **ClickUp API** — Comprehensive project management platform vs Prioritio's focused priority-based task tracking
- **Trello API** — Kanban-style board management vs Prioritio's priority-level-based task system

## FAQ

### Why is there no official OpenAPI spec for Prioritio API?

Prioritio does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Prioritio API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Prioritio API use?

The Prioritio API uses Bearer token authentication. Include your token in the Authorization header as 'Bearer your-token'. Through Jentic, the bearer token is stored encrypted in the credential vault and agents receive scoped access without handling raw credentials.

### What priority levels does the Prioritio API support?

The API supports four priority levels: low, medium, high, and critical. These are defined as an enum on the task priority field and also available through the GET /priorities endpoint which returns configuration details including level names and associated color codes.

### Can I filter tasks by status with the Prioritio API?

Yes. The GET /tasks endpoint accepts a status query parameter with values 'open', 'in_progress', or 'completed'. This allows you to retrieve only tasks in a specific workflow stage without client-side filtering. The endpoint also supports page and limit parameters for pagination.

### How do I create a task with a deadline through Jentic?

Search Jentic for 'create a prioritized task', load the createTask operation schema, and execute with a JSON body containing title (required), plus optional description, priority (low/medium/high/critical), and due_date in YYYY-MM-DD format. Install with pip install jentic and set your JENTIC_AGENT_API_KEY environment variable.

### What are the rate limits for the Prioritio API?

The Prioritio API specification does not document explicit rate limits. Standard API best practices apply. If you encounter throttling responses, implement exponential backoff in your retry logic.

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

Yes. Because you run Jentic One yourself, your own rules decide which Prioritio operations and credentials the agent can use. Prioritio puts the task id in the URL path at `/tasks/{id}`, so you can pin the agent to reading and updating specific tasks with GET `/tasks/{id}` and PUT `/tasks/{id}` while leaving out task creation. Operations you do not grant, such as POST /tasks or listing priority configurations, stay off limits unless you add them.