API v1 available

ProjectOps360 Developer Platform

Build connected project operations.

Use one versioned contract to read project truth, create governed work, receive signed events, connect AI agents through MCP, and automate workflows from the command line.

Quickstart

Authentication

Create a service account and scoped token inside ProjectOps360, then call the public API with a Bearer token.

Send the token in the Authorization header. Tokens begin with p360_ and are shown only once. Never place them in browser code or source control.

Base URL

https://projectops360.com/api/v1

Authorization

Bearer p360_••••••••••••••••

API resources

Reads are paginated and organization-scoped. Writes delegate to canonical ProjectOps360 commands and preserve audit provenance.

ResourceReadCreate
/projectsProjectsYes—
/milestonesMilestonesYesYes
/tasksTasksYesYes
/subtasksSubtasksYesYes
/dependenciesDependenciesYes—
/risksRisksYes—
/issuesIssuesYes—
/peoplePeopleYes—
/time-entriesTime entriesYes—
/eventsEventsYes—

Request examples

List projects

curl "https://projectops360.com/api/v1/projects?limit=10" \
  -H "Authorization: Bearer $PROJECTOPS360_TOKEN"

Create a task

curl -X POST "https://projectops360.com/api/v1/tasks" \
  -H "Authorization: Bearer $PROJECTOPS360_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"PROJECT_UUID","title":"Integration task","priority":"p2"}'

Scopes

Grant only the scopes the integration needs. Organization owners and admins can revoke a token immediately.

projects:readmilestones:readmilestones:writetasks:readtasks:writesubtasks:readsubtasks:writedependencies:readrisks:readissues:readpeople:readtime_entries:readevents:readwebhooks:managemcp:use
/api/v1/webhooks

Signed webhooks

Subscribe to canonical project events. Deliveries use POST, include a unique delivery identifier, retry transient failures, and sign the exact request body.

Verify x-projectops-signature with the webhook secret and reject stale x-projectops-timestamp values. Use x-projectops-delivery as the idempotency key.

/api/v1/mcp

MCP server

Connect compatible AI agents to the same governed API vocabulary. The MCP endpoint accepts JSON-RPC over POST; opening it directly in a browser is not a valid connectivity test.

initialize · tools/list · tools/call

cli/projectops360.mjs

Command line

The zero-dependency CLI supports list, get, create, and sequential task imports.

p360 list · get · create · import

Developer sandbox

The authenticated sandbox keeps the token only in the form, lets you select a resource, and executes real /api/v1 reads.

Open developer settings

Security model

Every token belongs to one organization and one service account. RBAC, RLS, explicit scopes, audit records, token hashing, signed delivery, retry controls, and canonical provenance remain enforced.