Cirqll API

Name: Cirqll API API
Brand: Cirqll API
Availability: InStock

✓ Official Vendor SpecProductivityTask Managementoauth26 EndpointsREST

For Agents

Read Cirqll customers and assignments, create tasks, and exchange OAuth 2.0 tokens to drive field-service automation. Six endpoints with read and write scopes.

Quickstart

Get started with Cirqll API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a task in Cirqll"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cirqll API API.

List Cirqll customers with pagination, filtering, and partial field selection

List assignments tied to customers for field-service scheduling

Create a new Cirqll task to drive an assigned worker through the next step

Exchange an OAuth 2.0 authorization code for a 15-day access token

Refresh an expired Cirqll access token via the refresh endpoint

GET STARTED

Start building with Cirqll API API

Explore with Jentic

View OpenAPI Document

Cirqll is a Dutch SaaS platform that gives field-service and operations teams a structured workflow over customers, assignments, and tasks. The Cirqll API exposes 6 endpoints over https://api.cirqll.nl, secured with OAuth 2.0 authorization-code flow that issues 15-day access tokens and 30-day refresh tokens with read and write scopes. The API supports pagination, filtering, ordering, eager loading, partial field selection, and webhook integrations for event-driven workflows so back-office systems and AI agents can read customer records, list assignments, and create tasks.

Use Cases

Patterns agents use Cirqll API API for, with concrete tasks.

★ Field-Service Task Creation From Inbound Email

When a customer email arrives at a service inbox, an automation can identify the customer, look up their open assignments via GET /assignments, and create a new task with POST /tasks linking it to the right assignment. Eager loading on the assignments endpoint pulls the customer record inline, removing a second round-trip.

GET /assignments?filter[customer_id]=12345&include=customer, then POST /tasks with the matching assignment_id and a description from the email body.

Customer Sync Into a Data Warehouse

An ETL job can paginate GET /customers nightly and load the records into a warehouse for analytics. Partial field selection keeps the payload small, and the OAuth refresh-token rotation lets the job run unattended for 30 days before re-authorisation. Cirqll's filtering and ordering mean only changed customers can be pulled.

GET /customers?fields=id,name,updated_at&filter[updated_after]=2026-06-01&page=1 and load each page into the warehouse staging table.

Token Lifecycle Automation

Long-running integrations need a clean refresh story. Cirqll's POST /oauth/token/refresh accepts a refresh token and returns a fresh access token within the 30-day refresh window. A scheduled job that rotates tokens proactively avoids the 401 failure mode common in OAuth integrations that only refresh on demand.

POST /oauth/token/refresh with the stored refresh token to obtain a new access token before the 15-day expiry.

AI Agent Service Dispatch

An AI dispatch agent invoked through Jentic can take an inbound request, identify the customer in Cirqll, and create a task on the appropriate assignment. Jentic holds the OAuth tokens in MAXsystem and refreshes them transparently, so the agent never handles credentials or runs into expired-token errors.

Search Jentic for 'create a task in Cirqll', load POST /tasks, and create a task linked to assignment 678 with the dispatched description.

Key Endpoints

6 endpoints — cirqll is a dutch saas platform that gives field-service and operations teams a structured workflow over customers, assignments, and tasks.

METHOD

PATH

DESCRIPTION

GET

/customers

List customers with pagination and filtering

GET

/assignments

List assignments with eager loading

POST

/tasks

Create a new task

GET

/oauth/authorize

OAuth 2.0 authorization endpoint

POST

/oauth/token

Exchange authorization code for access token

POST

/oauth/token/refresh

Refresh an expired access token

GET

/customers

List customers with pagination and filtering

GET

/assignments

List assignments with eager loading

POST

/tasks

Create a new task

GET

/oauth/authorize

OAuth 2.0 authorization endpoint

POST

/oauth/token

Exchange authorization code for access token

Why though Jentic?

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

Credential isolation

Cirqll OAuth 2.0 access and refresh tokens are stored encrypted in the Jentic vault (MAXsystem). Jentic manages refresh before the 15-day access-token expiry so agents never see a 401 mid-workflow.

Intent-based discovery

Agents search Jentic by intent (e.g., 'create a task in Cirqll') and Jentic returns POST /tasks with its input schema and the required write scope, so the agent can call the right endpoint without browsing Cirqll docs.

Time to first call

Direct Cirqll integration: 1-2 days for OAuth authorization-code flow, refresh logic, and pagination handling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Circle Community API

Circle hosts customer communities while Cirqll runs the operational task management.

Use Cirqll for the field-service task pipeline; use Circle for the customer-facing community space.

Complementary

CINNOX API

CINNOX manages the inbound customer conversation that triggers a Cirqll task.

Use CINNOX to capture the customer message; use Cirqll to convert it into a structured field-service task.

Complementary

Cisco API

Cisco infrastructure tooling complements Cirqll's customer and task workflows.

Use Cisco APIs for network diagnostics on a customer's site; use Cirqll to log the visit and follow-up tasks.

FAQs

Specific to using Cirqll API API through Jentic.

What authentication does the Cirqll API use?

Cirqll uses OAuth 2.0 authorization-code flow with 15-day access tokens and 30-day refresh tokens. Scopes are read and write. Through Jentic, both tokens are stored encrypted in the MAXsystem vault and refreshed automatically before expiry.

Can I create tasks programmatically with the Cirqll API?

Yes. POST /tasks creates a new task. Tasks are typically linked to assignments, which themselves belong to customers — fetch the assignment via GET /assignments first to obtain the assignment_id.

What are the rate limits for the Cirqll API?

Cirqll does not document hard rate limits in the OpenAPI spec; throttling is governed by your account tier. Plan paginated reads on /customers and /assignments and let Jentic surface 429 responses for retry.

How do I list Cirqll customers through Jentic?

Run pip install jentic, then search Jentic for 'list customers in Cirqll'. Jentic returns GET /customers with pagination and field-selection parameters in the schema. Execute it with the desired page and filter. Sign up at https://app.jentic.com/sign-up.

Does Cirqll support partial field selection?

Yes. The API supports the fields query parameter so a request like GET /customers?fields=id,name returns only those attributes. This is useful for syncing into a warehouse without pulling unused payload.

How long do Cirqll tokens last?

Access tokens are valid for 15 days; refresh tokens are valid for 30 days. Use POST /oauth/token/refresh proactively before the 15-day expiry to keep long-running integrations live without re-prompting the user.