canonical: https://jentic.com/apis/api.ontraccr.com/ontraccr

# Ontraccr Zapier Integration API

Jentic publishes the only available OpenAPI specification for Ontraccr Zapier Integration API, keeping it validated and agent-ready. Ontraccr is a construction operations platform, and this Zapier-facing API exposes a focused slice of its board, status, and card model so external automations can read project boards and create cards programmatically. The four endpoints cover health checking, listing boards, fetching the statuses configured on a board, and creating a card under a chosen status. Authentication uses an API key passed in the request, and the surface is intentionally narrow because it is designed to back Zapier triggers and actions rather than to expose the full Ontraccr platform.

## For AI agents

List Ontraccr project boards, read their status columns, and create new cards in a specific status - designed for Zapier-style triggers and actions.

## Scope

Does not handle time tracking, forms, scheduling, or invoicing - use for board, status, and card automation through the Zapier-facing surface only.

## Capabilities

- Verify connectivity and credentials with the GET `/zapier/status` health check
- List all project boards available to the authenticated account via `/zapier/boards`
- Read the status columns configured on a given board with `/zapier/boards/statuses`
- Create a new card on a specific board and status using `/zapier/boards/card`
- Drive Zapier-style automations that move work into Ontraccr from external triggers

## Use cases

### Form-to-Card Automation

Convert inbound form submissions, emails, or chat requests into Ontraccr cards by listing boards with `/zapier/boards`, looking up the target status via `/zapier/boards/statuses`, and creating the card with `/zapier/boards/card.` This avoids manual data entry for crews and dispatchers who would otherwise re-key job intake into Ontraccr.

Example prompt: Look up the board id named 'Service Requests', fetch its statuses, then POST `/zapier/boards/card` with title and description from the form payload assigned to the 'New' status.

### Board and Status Discovery

Expose Ontraccr's structure to a configuration UI so users can pick the right board and status when wiring up a Zap or other automation. `/zapier/boards` returns the list of boards and `/zapier/boards/statuses` returns the columns within each, providing the dropdown options without requiring users to copy identifiers from the Ontraccr web app.

Example prompt: Call GET `/zapier/boards`, then for each board call GET `/zapier/boards/statuses` and return a mapping of board name to status names.

### Health Check and Credential Validation

Confirm an Ontraccr API key is valid before running long-lived automations by calling `/zapier/status.` This is useful at deployment time and as part of scheduled credential rotations. A failure response signals that the key has been revoked or scoped away from the boards endpoints.

Example prompt: Call GET `/zapier/status` with the configured API key and report whether the key is currently authorised.

### AI Agent Construction Dispatch via Jentic

Have an agent triage incoming customer requests and create the appropriate Ontraccr card in the right board and status. Jentic returns the card-creation operation by intent, the agent supplies the parsed request data, and Jentic injects the API key from the vault - keeping construction-platform credentials out of the agent's prompt context.

Example prompt: Search Jentic for 'create an Ontraccr card', load the POST `/zapier/boards/card` schema, and execute with the board id, status id, and a title summarising the customer request.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/zapier/status` | Health check for the integration |
| GET | `/zapier/boards` | List available project boards |
| GET | `/zapier/boards/statuses` | List status columns on a board |
| POST | `/zapier/boards/card` | Create a new card on a board status |

## Key resources

- **Boards** — List boards visible to the authenticated account
- **Statuses** — Read status columns configured on a board
- **Cards** — Create cards under a chosen status
- **Status** — Health check for credentials and connectivity

## Why Jentic

- **Setup:** Wiring Ontraccr's Zapier surface by hand means setting up its API key header, learning the board and status shapes, and posting cards yourself. Through Jentic you install once, import Ontraccr from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Ontraccr's Zapier endpoints take the board target in the request body when creating a card, so scope the agent to the operations it needs, such as listing boards and creating a card, and leave out others unless you add them. You choose the allowed operations, so the agent only calls what you list.
- **Credential handling:** Your Ontraccr 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 'create a card on a board' or 'list board statuses', and Jentic returns the matching Ontraccr operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Procore API** — Construction management platform with deeper project, financials, and field operations coverage
- **monday.com API** — General-purpose work board platform with broader board and column types
- **Trello API** — Lightweight kanban platform for personal or non-construction boards

## FAQ

### Why is there no official OpenAPI spec for Ontraccr Zapier Integration API?

Ontraccr does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Ontraccr Zapier Integration API via 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 Ontraccr Zapier Integration API use?

The API uses an API key. The key is sent on each request and authorises access to the four /zapier/* endpoints. Through Jentic, the API key is stored encrypted in your Jentic One instance and injected when the operation is executed, so the raw key never enters the agent's prompt context.

### Can I create cards on a specific board status with the Ontraccr Zapier API?

Yes. Call POST `/zapier/boards/card` with a board identifier, a status identifier, and the card payload. Use GET `/zapier/boards` followed by GET `/zapier/boards/statuses` to look up the right identifiers if your automation does not already know them.

### What are the rate limits for the Ontraccr Zapier Integration API?

The spec does not declare numeric rate limits. Because the surface is narrow and aimed at Zapier-style automations, treat it as low-volume - bulk imports should pace requests, and any 429 response should be retried with exponential backoff.

### How do I create an Ontraccr card through Jentic?

Search Jentic for 'create an Ontraccr card', load the POST `/zapier/boards/card` schema, and execute with the board id, status id, and card details. With `pip install jentic` it is a single execute() call; the API key stays in your Jentic One instance.

### Does the API expose Ontraccr's full feature set?

No. This is the Zapier-facing surface, limited to listing boards, reading their statuses, creating cards, and a status check. Forms, scheduling, time tracking, and other Ontraccr modules are not exposed here and require the main Ontraccr application.

### Can I limit what my agent is allowed to do with the Ontraccr Zapier Integration API?

Yes. Jentic One is self-hosted, so you decide which of the Ontraccr operations your agent may call: for example, you can allow it to list boards with GET `/zapier/boards` and read columns with GET `/zapier/boards/statuses` while withholding card creation via POST `/zapier/boards/card.` Because the board target is passed in the request body when creating a card, you control the surface by choosing exactly which operations to expose and leaving the rest off. Your own rules also govern the credentials the agent uses, and your stored API key is injected at execution time rather than placed in the agent's prompt.