canonical: https://jentic.com/apis/5pmweb.com/5pmweb

# 5pmweb 5pm Project Management API

Jentic publishes the only available OpenAPI specification for 5pm Project Management API, keeping it validated and agent-ready. The 5pm Project Management API is the integration interface for the 5pm web platform, exposing thirteen endpoints that cover authentication, projects, tasks, activity, users, and project groups. Responses are returned as JSON or XML depending on the request, and authentication uses a session-style API key obtained from the signIn endpoint. The API is intended for embedding 5pm project data into reporting tools, replacing manual exports, or wiring 5pm to external systems.

## For AI agents

Authenticate against a 5pm workspace, list and edit projects and tasks, and pull activity and user records for reporting. Useful for agents syncing 5pm project state into other tools.

## Scope

Does not handle billing, time tracking exports, or workspace provisioning - use for project, task, activity, and user operations inside an existing 5pm account only.

## Capabilities

- Authenticate to a 5pm workspace and obtain a session token via signIn
- List, add, update, and remove projects under a 5pm account
- List, add, and update tasks attached to a project with assignees and due dates
- Retrieve activity feeds covering project and task changes over a time window
- Look up users and project group membership inside a 5pm workspace

## Use cases

### Sync 5pm Projects into a Reporting Warehouse

Operations and analytics teams pull project, task, and activity records out of 5pm on a schedule and load them into a warehouse for cross-tool reporting. The /service/get/projects/getAll, /service/get/tasks/getList, and activity endpoints return paginated data suitable for incremental sync. A first working pipeline takes a developer one to two days versus building a manual CSV export workflow.

Example prompt: Authenticate via /service/get/authentication/signIn, then call /service/get/projects/getAll and /service/get/tasks/getList and write the records to a target warehouse table with timestamps.

### Programmatic Project Setup from a CRM Win

Sales operations teams that win a deal in their CRM use the 5pm API to spin up a project and its initial tasks without manual data entry. The /service/get/projects/add and /service/get/tasks/add endpoints accept the project name, owner, and task list, so a single agent run replaces a templated setup checklist. End-to-end automation takes around a day to wire up.

Example prompt: Call /service/get/projects/add to create 'Acme Implementation', then call /service/get/tasks/add three times to seed kickoff, planning, and review tasks with due dates.

### Project Activity Dashboards

Project managers running a portfolio across 5pm pull the activity endpoint into a dashboard to see who is moving work and where things have stalled. The activity feed surfaces change events scoped to projects and users, replacing manual status meetings with a live view. A simple dashboard build is roughly two days.

Example prompt: Pull the activity feed for the Q3 Roadmap project, group entries by user, and produce a summary of task updates from the last seven days.

### AI Agent Project Assistant via Jentic

An AI assistant connected through Jentic can answer questions like 'what is on my plate in 5pm this week' by calling the tasks and users endpoints behind the scenes. Jentic handles the signIn flow and stores the API key in the vault, so the agent only needs to express the natural-language intent. End-to-end response time is under thirty seconds.

Example prompt: Search Jentic for 'list my 5pm tasks', load /service/get/tasks/getList, filter to tasks assigned to the current user, and return them sorted by due date.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /service/get/authentication/signIn | Sign in and obtain a session API key |
| GET | /service/get/projects/getAll | List all projects in the workspace |
| GET | /service/get/projects/add | Create a new project |
| GET | /service/get/projects/update | Update an existing project |
| GET | /service/get/tasks/getList | List tasks scoped to a project or user |
| GET | /service/get/tasks/add | Create a new task under a project |

## Key resources

- **Authentication** — Session sign-in to obtain an API key for subsequent calls
- **Projects** — Project records with name, owner, status, and group membership
- **Tasks** — Tasks under a project with assignee, due date, and status
- **Activity** — Activity feed of project and task changes over a window
- **Users and Groups** — Workspace users and project group membership

## Why Jentic

- **Setup:** Wiring the 5pm Project Management API by hand means managing its API key, resolving your account host, and calling the signIn flow to get a session key before each batch of work. Through Jentic you install once, import the 5pm Project Management API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** 5pm carries project and task selectors in query parameters rather than a resource id in the path, so limit the agent to the operations it needs, such as listing projects or tasks, and leave out adding or updating projects unless you add them. You choose the allowed set, so only the operations you pick can run.
- **Credential handling:** Your 5pm API key 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 'list 5pm projects' or 'get the tasks in a project', and Jentic returns the matching 5pm operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana API** — Larger project management platform with deeper task hierarchies and SDKs
- **Basecamp API** — Project communication and to-do API with a simpler model
- **ClickUp API** — Task management API with extensive automation and views
- **monday.com API** — Board-based work management API often paired with project tools for cross-team views

## FAQ

### Why is there no official OpenAPI spec for 5pm Project Management API?

5pm publishes HTML developer documentation but does not distribute a machine-readable OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call 5pm 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 5pm Project Management API use?

The API uses a session-style API key. Call GET /service/get/authentication/signIn with workspace credentials to receive a key, then pass that key on subsequent requests. When called through Jentic the credential is held in the vault and attached at execution time so it never appears in agent context.

### Can I create projects and tasks programmatically with the 5pm Project Management API?

Yes. Call /service/get/projects/add to create a project and /service/get/tasks/add to seed tasks. Each task accepts a project ID, name, assignee, and due date. Update and removal endpoints exist for both resources.

### What are the rate limits for the 5pm Project Management API?

5pm does not publish a numeric rate limit. Treat the API as fair-use, cache reads where possible, and back off on HTTP 429 responses. Avoid tight polling loops against /service/get/projects/getAll on large accounts; refresh on a one-to-five-minute interval instead.

### How do I list my 5pm tasks through Jentic?

After running pip install jentic and setting JENTIC_AGENT_API_KEY, search Jentic for 'list 5pm tasks', load /service/get/tasks/getList, and execute. Jentic injects the session key and returns the structured task list to the agent.

### Does the 5pm Project Management API return JSON or XML?

Both. The path prefix /service/get/ indicates a GET-style call and the response format follows the Accept header or query parameter your client provides. JSON is the default when calling via Jentic; XML is supported for legacy clients.

### Can I limit what my agent is allowed to do with the 5pm Project Management API?

Yes. Jentic One runs on your own infrastructure, so your rules decide which 5pm operations and credentials the agent can use. Because 5pm carries project and task selectors in query parameters rather than in the path, you scope access by picking the exact operation set the agent may call, for example limiting it to read-only listing through /service/get/projects/getAll and /service/get/tasks/getList while leaving out /service/get/projects/add and /service/get/tasks/add. Only the operations you allow can run, and the stored API key is attached at execution time rather than exposed to the agent.