Productivity Endpoints
Use public API endpoints for projects, tasks, and time entries.
Productivity public API endpoints are available under /public/v1.
Resources
/projects/tasks/time-entries
Use these endpoints when another system needs to create or sync project work, task assignments, or time tracking records.
Common Integration Patterns
Use Productivity endpoints when a trusted backend system needs to keep delivery work aligned with another tool. Typical examples include creating an Agiled project after a signed contract, creating tasks from an implementation checklist, or syncing approved time entries into an external reporting system.
Keep ownership clear. If another system creates projects or tasks, decide which system owns status changes, assignments, and due dates before enabling two-way sync. Otherwise users can see records move back and forth unexpectedly.
Useful Includes
- Projects:
owner,members - Tasks:
project,assigned_user,assignees - Time entries:
project,task,user
Use includes when the integration needs display context in one response. Avoid requesting includes that are not needed for a background sync job, because large relationship payloads can slow imports and make retry logs harder to read.
Before Creating Records
Validate these fields in your source system before sending data to Agiled:
- Project names and customer/account references.
- Task titles, status, due date, project, and assignee mapping.
- Time entry date, duration, user, project, task, and notes.
- External IDs or idempotency keys if your integration retries writes.
Use a read-only API key for reporting and audit exports. Use a full-access key only when the integration must create, update, or delete records.
Sync Safely
For imports, start with a small page size or a limited date range. Confirm the created projects, tasks, and time rows from the Agiled UI before running a broad backfill. For recurring sync, store the Agiled record IDs returned by create requests so later updates target the correct records.
Project And Task Ownership
Choose one owner for each synced workflow. If Agiled owns project delivery, external systems should avoid overwriting task owners, statuses, dates, or milestones after the team starts work. If the external system owns planning, make that clear to users so they know where to make lasting changes.
For time entries, verify user mapping before import. Time rows attached to the wrong user, project, or task can affect billing, reports, and payroll review.