5day.io API
Agent-ready OpenAPI document · curated by JenticProductivityTask Managementbearer17 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Register integrations, trigger and execute workflows, manage webhooks, and push events into 5day.io project workspaces. Useful for agents wiring 5day projects into external automations.
Use for: Register a new integration between 5day.io and our internal CRM, Trigger the onboarding workflow for a newly signed customer, List all workflow runs that failed in the last 24 hours, Set up a webhook that fires when a project status changes
Not supported: Does not handle 5day.io billing, user account creation, or core task UI rendering - use for integration, workflow, webhook, and event operations only.
Jentic publishes the only available OpenAPI specification for 5day.io API, keeping it validated and agent-ready. The 5day.io API exposes the integration service that drives 5day.io's project and work management platform, covering integrations, workflows, webhooks, and event subscriptions across seventeen endpoints. Teams use it to register external integrations, run automated workflows, push and receive events, and link 5day projects to outside systems. Authentication is bearer token using credentials issued from a workspace's integration settings.
Install Jentic One Beta
Connect the 5day.io API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 5day.io 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F5day.io%2F5day-io" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F5day.io%2F5day-io" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 5day.io API.
Register and update third-party integrations connected to a 5day.io workspace
Trigger workflow executions with structured input payloads
List historical workflow runs and inspect their status
Subscribe to events through webhooks with filterable trigger types
Publish custom events that fan out to subscribed workflows
Rotate or revoke webhook signing secrets without manual portal access
Use Cases
Patterns agents use 5day.io API for, with concrete tasks.
★ Connect 5day.io Projects to External Systems
Operations teams use the integrations endpoints to register connections between 5day.io and CRMs, helpdesks, or finance tools so that activity in those systems creates or updates 5day projects automatically. The /integrations and /integrations/{id} endpoints expose CRUD-style operations that replace per-tenant configuration scripts. A typical connection takes one to two days of development versus building and hosting a custom middleware service.
Call POST /integrations to register a Salesforce integration with the workspace's API token, then verify the connection is active by calling GET /integrations/{id}.
Trigger Project Workflows on External Events
Companies that automate onboarding, project kickoff, or recurring reviews publish events into 5day.io and let workflows fan out the resulting tasks. The /workflows/{id}/execute endpoint accepts a structured payload and runs the configured workflow, while /events allows agents to publish arbitrary domain events without hardcoding workflow IDs. Setup is roughly a day for a basic workflow and three to four days for a multi-stage automation.
Call POST /events with type 'customer_signed' and customer details, then poll GET /workflows/{id} to confirm the onboarding workflow ran to completion.
Webhook Subscriptions for Real-Time Project Events
Engineering teams that need a live feed of project changes register webhooks against the 5day.io workspace. The /webhooks endpoints let an agent enumerate, create, and rotate subscriptions with filterable event types, replacing manual portal configuration. A webhook subscription with handler code is typically a half-day to ship.
Call POST /webhooks with a callback URL and event filter for 'project.status_changed', then verify by triggering a status change and confirming the callback receives the event.
Agent-Managed 5day.io Operations via Jentic
AI agents connected through Jentic can keep 5day.io workspaces in sync with other tools by calling the integrations, workflows, and webhooks endpoints in a single conversation. Jentic returns the operation schema and stores the bearer token in the vault, so the agent does not see credentials and does not need a hand-rolled SDK. End-to-end time from intent to result is under a minute.
Search Jentic for 'trigger a 5day workflow', load the /workflows/{id}/execute schema, and execute the onboarding workflow with the new customer payload.
Key Endpoints
17 endpoints — jentic publishes the only available openapi specification for 5day.
METHOD
PATH
DESCRIPTION
GET
/integrations
List registered integrations
POST
/integrations
Register a new integration
GET
/workflows
List workflows in the workspace
POST
/workflows/{id}/execute
Execute a workflow with an input payload
POST
/webhooks
Create a webhook subscription
POST
/events
Publish a custom event into the workflow engine
GET
/integrations
List registered integrations
POST
/integrations
Register a new integration
GET
/workflows
List workflows in the workspace
POST
/workflows/{id}/execute
Execute a workflow with an input payload
POST
/webhooks
Create a webhook subscription
POST
/events
Publish a custom event into the workflow engine
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the 5day.io API by hand means managing its bearer token, targeting the gateway.5day.io v1 base, and shaping integration, workflow, and webhook payloads yourself. Through Jentic you install once, import the 5day.io API from the API Directory, store the token once, and your agent calls it.
Permission scoping
5day.io puts the workflow id in the URL path (/workflows/{id}/execute), so a rule can pin your agent to executing one workflow. You choose the operations it may call, so creating integrations or webhooks is not included unless you add them.
Credential isolation
Your 5day.io 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.
Intent-based discovery
Agents search Jentic by intent such as 'trigger a 5day workflow' or 'subscribe to 5day events', and Jentic returns the matching 5day.io operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using 5day.io API through Jentic.
Why is there no official OpenAPI spec for 5day.io API?
5day.io publishes Swagger UI for its integration service but does not distribute a downloadable OpenAPI document for direct ingestion. Jentic generates and maintains this spec so AI agents and developers can call 5day.io through 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 5day.io API use?
The API uses HTTP bearer authentication. A workspace administrator generates a token in 5day.io's integration settings and the token is sent in the Authorization header. When called through Jentic the token is held in the encrypted vault and attached at execution time so it never enters the agent's context.
Can I trigger a 5day.io workflow programmatically?
Yes. Call POST /workflows/{id}/execute with the workflow ID and an input payload that matches the workflow's expected schema. The response includes a run ID you can poll via GET /workflows/{id} to inspect status.
What are the rate limits for the 5day.io API?
5day.io does not publish a numeric rate limit on its developer documentation. Plan for fair-use limits based on your workspace tier and back off on HTTP 429 responses. For high-volume event publishing, batch requests where the API supports it and avoid tight polling loops on /workflows.
How do I subscribe to 5day.io project events through Jentic?
After running pip install jentic and setting JENTIC_AGENT_API_KEY, search Jentic for 'subscribe to 5day events', load the POST /webhooks schema, and execute it with your callback URL and event filter. Jentic returns the webhook ID and signing secret in the response.
Is the 5day.io API available on the free plan?
API access is gated by 5day.io's paid plans. Check the workspace settings panel under Integrations to confirm whether the integration service is enabled for your subscription tier before issuing tokens.
Can I limit what my agent is allowed to do with the 5day.io API?
Yes. Because you run Jentic One yourself, your own rules decide which 5day.io operations and credentials the agent may use. Since 5day.io carries the workflow id in the URL path (/workflows/{id}/execute), a rule can pin the agent to executing a single workflow. You pick the operations it can call, so creating integrations via POST /integrations or subscribing webhooks via POST /webhooks stays off limits unless you explicitly grant them.
GET STARTED