Favro API

Name: Favro API API
Brand: Favro API
Availability: InStock

✓ Official Vendor SpecProductivityTask Managementbasic65 EndpointsREST

For Agents

Create and move cards across columns, manage backlogs and boards (widgets), capture comments, and track dependencies on a Favro workspace.

Connect the Favro API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Favro API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Favro API API.

Create cards on a board or backlog with title, description, and assignment via POST /cards

Move cards across columns by updating columnId via PUT /cards/{cardId} for kanban transitions

Attach files to cards via POST /cards/{cardId}/attachment for design assets and documentation

Manage card dependencies via /cards/{cardId}/dependencies to model blocked-by relationships

GET STARTED

Start building with Favro API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Favro API API for, with concrete tasks.

★ Issue Triage Bot for Engineering Teams

Engineering teams using Favro for sprint planning auto-create cards from incoming bug reports or support escalations. The agent POSTs to /cards with the report content and assigns it to the right widget. Cuts triage latency and keeps the support-to-engineering trail in Favro instead of email.

On receipt of a support escalation, POST /cards with title, description, and the engineering widget's id, then return the card url to the support agent

Kanban State Sync with External Tools

Teams running mixed toolchains keep Favro card state in sync with deployment systems by updating columnId via PUT /cards/{cardId} when external events fire. The pattern moves a card to 'Done' when CI publishes a release, for example. Removes manual board updates from the engineering routine.

On a release-published webhook, PUT /cards/{cardId} with the Done columnId and post a comment summarising the release

Dependency Mapping and Reporting

Programme managers map dependencies between cards using /cards/{cardId}/dependencies and pull activity timelines from /cards/{cardId}/activities for status reports. The combination supports critical-path analysis and weekly report automation. Useful for multi-team programme work.

GET dependencies for each card on a release widget and produce a graph showing blocked-by chains

Activity Audit for Compliance

Regulated teams pull /cards/{cardId}/activities to build immutable audit logs of who changed what and when. The activity feed includes column moves, assignment changes, and edits. Saves a manual export step for audits that need a full change history.

For each card in a compliance scope, GET /cards/{cardId}/activities and write the entries to a long-term audit store

AI Project Manager Agent via Jentic

Conversational PM agents use Jentic to call Favro from natural-language requests like 'create a card on the design backlog with these notes'. Jentic resolves the intent to POST /cards and supplies basic-auth credentials from the vault. Cuts integration time from days to under an hour and prevents the agent from handling raw passwords.

Through Jentic, search 'create a card in favro', load POST /cards, and execute with title, description, and widget id parsed from the user's prompt

Key Endpoints

65 endpoints — the favro api is the planning platform's full backend for managing organizations, collections, widgets (boards and backlogs), columns, cards, comments, tags, tasks, and task lists.

METHOD

PATH

DESCRIPTION

POST

/cards

Create a card on a widget

PUT

/cards/{cardId}

Update card fields including column

POST

/cards/{cardId}/attachment

Attach a file to a card

GET

/cards/{cardId}/activities

List card activity history

POST

/cards/{cardId}/dependencies

Add a dependency between cards

GET

/widgets

List widgets (boards and backlogs)

GET

/columns

List columns on a widget

POST

/cards

Create a card on a widget

PUT

/cards/{cardId}

Update card fields including column

POST

/cards/{cardId}/attachment

Attach a file to a card

GET

/cards/{cardId}/activities

List card activity history

POST

/cards/{cardId}/dependencies

Add a dependency between cards

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Favro basic-auth credentials (email + token) are stored encrypted in the Jentic vault. Agents call operations by intent and Jentic injects the Authorization header at execution time — credentials never enter prompt context.

Intent-based discovery

Agents search 'create a card in favro' and Jentic returns POST /cards with its widget-id schema, so the agent can act without browsing the 65-endpoint surface.

Time to first call

Direct integration: 3-5 days across auth, the breadth of endpoints, and the collection-widget-column-card hierarchy. Through Jentic: under an hour per intent — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Trello

Card-based kanban tool with a simpler hierarchy

Choose Trello when the team uses single-board kanban; choose Favro for collections-and-widgets multi-team planning

Alternative

Asana

Task management alternative with strong project and portfolio views

Choose Asana for task-list-driven teams; choose Favro for kanban-first agile delivery with backlogs and dependencies

Alternative

monday.com

Work management platform with custom-board flexibility

Choose monday.com for highly custom board structures; Favro is more opinionated about agile patterns

Alternative

ClickUp

All-in-one work platform with broader feature coverage

Choose ClickUp when you need docs, goals, and chat in one tool; Favro focuses on planning and delivery boards

FAQs

Specific to using Favro API API through Jentic.

What authentication does the Favro API use?

Favro uses HTTP Basic authentication — supply your Favro email and an API token in the Authorization header. Through Jentic both halves of the basic-auth credential live in the vault and are injected at execution time, never entering the agent's prompt.

Can I create and move cards with the Favro API?

Yes. POST /cards creates a card on a widget and PUT /cards/{cardId} updates its columnId to move it through stages. Use GET /columns to discover the column ids available on a given widget.

What are the rate limits for the Favro API?

Favro does not document fixed rate limits in the OpenAPI spec — the live API returns rate-limit headers per response. Read the headers, batch reads where possible, and back off on 429 responses to stay within capacity.

How do I create a card through Jentic?

Install with pip install jentic, search 'create a card in favro', load POST /cards, and execute with the widget id, title, and description from your prompt. Sign up at https://app.jentic.com/sign-up.

Does the Favro API support card dependencies?

Yes. POST /cards/{cardId}/dependencies adds a dependency from one card to another, GET returns existing dependencies, and DELETE removes them. Use this to model blocked-by relationships and build critical-path reports.