Assignar Public API

Name: Assignar Public API
Brand: Assignar Public API
Availability: InStock

✓ Official Vendor SpecProductivityTask Managementoauth285 EndpointsREST

For 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.

Install Jentic One Beta

Connect the Assignar Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Assignar Public 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Assignar Public API.

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

GET STARTED

Start building with Assignar Public API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Assignar Public API for, with concrete tasks.

★ 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.

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.

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.

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 MAXsystem, 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.

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

85 endpoints — the assignar public api gives construction subcontractors and self-perform general contractors programmatic access to the assignar workforce and asset management platform.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Assignar OAuth 2.0 client credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped access token at runtime — the client secret never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'allocate a worker to a project') and Jentic returns the matching Assignar operation with its input schema, so the agent can call POST /allocations without browsing the spec.

Time to first call

Direct Assignar integration: 2-4 days for OAuth setup, schema mapping across 85 endpoints, and error handling. Through Jentic: under an hour — search, load, execute.

FAQs

Specific to using Assignar Public API through Jentic.

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.

Assignar Public API

Connect the Assignar Public API to your agent

Capabilities

Start building with Assignar Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs