Checkmob API

Name: Checkmob API API
Brand: Checkmob API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask Managementbearer50 EndpointsREST

For Agents

Manage Checkmob clients, work orders, services, questionnaires, and users so an agent can dispatch field jobs, pull checklist answers, and sync field data with other systems.

Quickstart

Get started with Checkmob 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 checkmob work order"

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

Capabilities

What an agent can do with Checkmob API API.

Create, list, update, activate, and deactivate client records

Create and look up work orders dispatched to field technicians

List services and checklist questionnaires tied to a client

Pull checklist answers captured by technicians on site

Provision users and assign them to groups or segments

GET STARTED

Start building with Checkmob API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Checkmob API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Checkmob API, keeping it validated and agent-ready. Checkmob is a Brazil-headquartered field service management platform used to dispatch technicians, track work orders, and capture data from the field on mobile devices. The API spans 50 endpoints across clients, addresses, work orders, services, checklists, questionnaires, users, segments, and custom fields, with a token-exchange flow for authentication. It is suited to teams integrating field operations with their CRM, billing, or BI stack.

Use Cases

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

★ Field Work Order Dispatch

Mirror work orders between an internal scheduling system and Checkmob so technicians see assignments on their mobile app. Listing work orders via /api/OrdemServico/List shows current state, and /api/OrdemServico/Post creates new orders when scheduling produces a job. Useful for service businesses already running a homegrown scheduler.

Create a work order via /api/OrdemServico/Post for client_id 42 with service_type 'maintenance' scheduled for 2026-06-15.

Checklist Answer Sync

Pull checklist answers captured by field technicians into a BI tool or QA dashboard. /api/RespostasQuestionario/List returns the answers for a given questionnaire and date range, which a scheduled job can normalise into a warehouse. Useful for compliance reviews or customer-facing service reports.

Pull /api/RespostasQuestionario/List for questionnaire_id 7 over the last 7 days and return the count of completed responses.

Client and Segment Management

Provision new clients in Checkmob from a CRM and slot them into the right segment so the field team picks up the relationship correctly. /api/Cliente/Post creates the client, /api/Endereco/Post adds an address, and /api/SegmentoClientes/Add links them to one or more segments for routing.

Create a client via /api/Cliente/Post named 'Acme Co', add an address, and link them to segment_id 3.

AI Agent for Field Service Operations

An autonomous agent receives natural-language requests from a dispatcher ('schedule a maintenance visit for Acme tomorrow', 'how many open jobs does Maria have?') and translates them into Checkmob calls through Jentic. The bearer token never enters the agent's prompt — Jentic handles token exchange and injection.

Through Jentic, search 'create a work order', load the schema for /api/OrdemServico/Post, and execute with the requested client and service type.

Key Endpoints

50 endpoints — jentic publishes the only available openapi specification for checkmob api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/Cliente/Post

Create a client

POST

/api/Cliente/List

List clients

POST

/api/OrdemServico/Post

Create a work order

POST

/api/OrdemServico/List

List work orders

POST

/api/RespostasQuestionario/List

Pull checklist answers

POST

/api/Usuario/Post

Create a user

GET

/token

Request an access token

POST

/api/Cliente/Post

Create a client

POST

/api/Cliente/List

List clients

POST

/api/OrdemServico/Post

Create a work order

POST

/api/OrdemServico/List

List work orders

POST

/api/RespostasQuestionario/List

Pull checklist answers

POST

Why though Jentic?

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

Credential isolation

Checkmob bearer tokens (and the upstream credentials used to mint them at /token) are stored encrypted in the Jentic MAXsystem vault. The agent never sees the raw token — Jentic handles the token-exchange flow and refresh.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a work order' or 'pull checklist answers') and Jentic returns the matching Checkmob operation with its input schema, so the agent picks the right call among 50 endpoints without browsing docs.

Time to first call

Direct Checkmob integration: 2-4 days for the token-exchange flow, Portuguese-language endpoint naming, and resource model. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Checkfront API

Booking management — different domain (customer reservations vs field technician dispatch)

Choose Checkfront when the use case is customer-driven bookings; Checkmob is for dispatching field technicians

Complementary

Chatwoot

Customer support platform you can pair with Checkmob to track field-related tickets

Choose Chatwoot when the customer-facing channel is conversation; pair with Checkmob for field execution

Complementary

Checkly Public API

Synthetic monitoring you can use to verify Checkmob endpoints stay reachable

Choose Checkly to set up uptime checks for the Checkmob production API

FAQs

Specific to using Checkmob API API through Jentic.

Why is there no official OpenAPI spec for Checkmob API?

Checkmob does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Checkmob API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Checkmob API use?

Checkmob uses HTTP bearer authentication. You exchange credentials at GET /token to receive a bearer token, which is then sent in the Authorization header on subsequent requests. Through Jentic, both the credentials and the resulting token are stored encrypted in the MAXsystem vault, and Jentic refreshes the token transparently.

Can I create work orders with the Checkmob API?

Yes. POST /api/OrdemServico/Post creates a new work order tied to a client and service type. /api/OrdemServico/List returns existing orders with filters, and /api/OrdemServico/Get fetches a specific order by ID.

How do I read checklist answers via the Checkmob API?

Use POST /api/RespostasQuestionario/List with the questionnaire and date range. The endpoint returns the completed responses captured by technicians on the mobile app, which you can then transform into reports or compliance evidence.

What are the rate limits for the Checkmob API?

The OpenAPI specification does not declare formal rate limits. Plan for retry-with-backoff on 429 responses and avoid polling /api/OrdemServico/List in tight loops — pull on a schedule and react to webhooks if available.

How do I create a Checkmob work order through Jentic?

Install the SDK with `pip install jentic`, then call Jentic.search('create a work order'), load the schema for /api/OrdemServico/Post, and execute with the client_id, service_type, and scheduled date. Jentic handles the /token exchange and bearer injection.