canonical: https://jentic.com/apis/assignar.com/assignar # Assignar Public API The Assignar Public API gives construction subcontractors and self-perform general contractors programmatic access to the Assignar workforce and asset management platform. It exposes activities, allocations, assets, clients, contacts, orders, projects, site diaries, skills, and timesheet data so back-office systems can keep crew schedules, equipment movements, and field reporting aligned. Endpoints support both batch operations on collections and granular updates to individual records keyed by ID. ## For AI agents Schedule field crews, assign equipment, and pull site diary or timesheet data from Assignar to keep construction operations in sync with payroll, ERP, and project management systems. ## Scope Does not handle accounting, invoicing, or payroll calculation - use for construction workforce, asset, and field reporting management only. ## Capabilities - Allocate workers and assets to specific projects, shifts, and orders through the /allocations and /orders resources - Pull and reconcile site diary entries, timesheets, and activity logs for payroll and progress reporting - Maintain a register of assets with utilisation, location, and assignment history via the /assets endpoints - Manage client and contact records tied to projects to keep CRM and operational data aligned - Track skills, qualifications, and licensing expiry against individual workers for compliance reporting - Create and update project records with start, end, and status fields to drive scheduling automations ## Use cases ### Crew and Asset Scheduling Sync Construction operations teams use Assignar to allocate workers, vehicles, and equipment to live projects. The API lets a scheduling agent read open allocations, push new assignments through POST /allocations, and reconcile asset usage against /assets so dispatch boards stay accurate without double-handling. Initial sync of an active project portfolio typically takes a few hours of integration work. Example prompt: Create an allocation linking worker ID 4421 to project ID 88 for shift 2026-06-10 06:00-14:30 and confirm the allocation ID returned ### Site Diary and Timesheet Reporting Field supervisors capture daily site diaries and worker timesheets in Assignar. The API exposes /site-diaries and /timesheets so a reporting agent can pull entries by date range, normalise them into a payroll or BI system, and surface variances against allocated hours. This removes manual exports and keeps payroll cycles closing on time. Example prompt: Fetch all timesheets between 2026-06-01 and 2026-06-07 for project ID 102 and flag any worker with more than 60 logged hours ### Compliance and Skills Tracking Subcontractors must track licences, tickets, and inductions across hundreds of workers. The API lets agents query the /skills resource and worker records to surface expiring qualifications before crews are assigned to a job that requires them. Combined with allocations, this lets a compliance agent block a placement if a required ticket has lapsed. Example prompt: List all workers whose White Card qualification expires within the next 30 days and surface their current allocations ### Agent Integration via Jentic Through Jentic, an AI agent discovers Assignar operations by intent (such as 'allocate a worker to a project') without parsing the OpenAPI spec or hard-coding endpoint paths. Jentic stores the OAuth 2.0 credentials in your Jentic One instance, returns a scoped access token at runtime, and validates the request payload before the call hits Assignar. This collapses a typical Assignar integration from days to under an hour for the common scheduling and reporting flows. Example prompt: Use Jentic to search for 'allocate a worker to a project', load the operation schema, and execute the call against the Assignar staging environment ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/allocations` | List worker and asset allocations across projects | | GET | `/activities` | List activity records linked to projects and orders | | POST | `/activities` | Create an activity record | | GET | `/assets` | List the asset register | | POST | `/assets` | Create an asset record | | GET | `/projects` | List active and historical projects | | GET | `/site-diaries` | List site diary submissions | ## Key resources - **Activities** — List, create, update, and delete activity records linked to projects and orders - **Allocations** — Read worker and asset allocations against projects and shifts - **Assets** — Manage the equipment register with assignment, location, and utilisation data - **Clients and Contacts** — Maintain client organisation and contact records tied to projects - **Projects** — Track project records with status, start and end dates, and related allocations - **Site Diaries** — Pull daily site diary entries submitted by field supervisors - **Skills** — Maintain the qualifications and licensing register against workers - **Timesheets** — Read worker timesheets for payroll and reporting reconciliation ## Why Jentic - **Setup:** Wiring Assignar by hand means running its OAuth 2.0 client-credentials flow against its Australian host and picking a path for allocations, activities, and assets. Through Jentic you install once, import the Assignar Public API from the API Directory, store the client credentials once, and your agent calls it. - **Permission scoping:** Assignar reaches allocations, activities, and assets through collection endpoints and request bodies rather than a resource id in the URL path, so limit the agent to the operations it needs, such as allocating a worker or listing assets. You choose the operations it may call, so creating assets is not included unless you add it. - **Credential handling:** Your Assignar client credentials are stored once, encrypted, by your own Jentic One instance and exchanged for a scoped access token at execution time. The client secret never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'allocate a worker to a project', and Jentic returns the matching Assignar operation with its input schema so the agent calls the right endpoint without browsing the spec. ## Related APIs - **Procore** — Construction project management platform commonly integrated alongside field workforce tools - **SyncroMSP** — Field service and asset management platform used by service businesses - **Smartsheet** — Spreadsheet-based work management often used to mirror Assignar schedules into shared sheets ## FAQ ### What authentication does the Assignar Public API use? The Assignar Public API uses OAuth 2.0. Through Jentic, the OAuth credentials are held in the encrypted vault and a scoped access token is exchanged at call time, so the raw client secret never enters the agent's context. ### Can I pull worker timesheets for payroll with the Assignar Public API? Yes. The /timesheets endpoint returns worker timesheet records, which can be filtered to a date range and reconciled against the /allocations endpoint for payroll close. A typical agent flow lists timesheets for the pay period, then cross-checks them against allocated hours per worker. ### What are the rate limits for the Assignar Public API? Assignar does not publish a fixed rate limit in the spec. Production accounts are throttled per tenant - the safest pattern is to back off on HTTP 429 responses and batch reads of /allocations or /timesheets by date range rather than polling per worker. ### How do I allocate a worker to a project through Jentic? Search Jentic for 'allocate a worker to a project', load the POST /allocations schema, and execute with the worker ID, project ID, and shift window. Jentic injects the OAuth token and validates the body before the request hits api.assignar.com.au/v2. ### Can I track qualification expiry with the Assignar Public API? Yes. The /skills resource lets you read each worker's qualifications and expiry dates. An agent can poll for skills expiring inside a window and cross-reference /allocations to flag any upcoming shift that requires a lapsed ticket. ### Which Assignar region does the API serve? The default base URL is https://api.assignar.com.au/v2 for Australian tenants, with https://api.assignar.com/v2 listed for other regions. Pick the server matching your tenant before issuing requests. ### Can I limit what my agent is allowed to do with the Assignar Public API? Yes. Because you self-host Jentic One, your own rules decide which Assignar operations and credentials the agent may use, so you can restrict it to just the calls it needs, such as listing assets or allocating a worker. Assignar reaches allocations, activities, and assets through collection endpoints and request bodies rather than a resource ID in the URL path, so you scope the agent at the operation level rather than by record. Since you choose the operations, an action like creating an asset is not available to the agent unless you explicitly grant it.