MotionOps API

Name: MotionOps API API
Brand: MotionOps API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybearer9 EndpointsREST

For Agents

Authenticate to MotionOps and register external webhook handlers that receive field-service events such as job updates, account changes, and tag triggers.

Connect the MotionOps API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 MotionOps API API.

Log into MotionOps via /login to receive a bearer token for subsequent calls

Log out of an active MotionOps session via /logout

Find an existing external webhook account through /external-webhook-account-find

GET STARTED

Start building with MotionOps API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for MotionOps API, keeping it validated and agent-ready. MotionOps is a field service management platform whose Open API exposes account login and logout flows alongside external webhook account management. The 9 endpoints cover authentication, registering and finding webhook accounts, tagging webhook accounts, and registering external webhook handlers by type. Authentication uses bearer tokens issued by /login.

Use Cases

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

★ Field Service Event Integration

Operations teams that want MotionOps job and account events flowing into their internal systems register an external webhook account, attach handlers per event type, and authenticate ongoing reads with the bearer token from /login. This wires field service activity into ticketing, billing, or analytics pipelines without polling.

Log in via /login, register a webhook account via /external-webhook-accounts, then attach a handler URL via /external-webhook/{webhookType}.

Webhook Account Tagging for Multi-Tenant Routing

When a service partner manages many MotionOps tenants, tags on external webhook accounts let them route inbound events to the right downstream system. The /external-webhook-account-tags endpoint manages those labels so a single endpoint can fan out to per-tenant handlers downstream.

Find an external webhook account by ID, then add a tenant-id tag via /external-webhook-account-tags so downstream routing can dispatch on it.

Agent-Driven Webhook Setup via Jentic

An operations agent provisioning a new MotionOps integration searches Jentic for the login and webhook registration operations, loads the schemas, and executes them in sequence. The agent never holds the long-lived MotionOps credentials — Jentic injects them — and receives only the resulting bearer token and webhook account ID.

Search Jentic for 'register a MotionOps external webhook', load /external-webhook-accounts, and execute it after acquiring a bearer token from /login.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/login

Authenticate and receive a bearer token

POST

/logout

Invalidate the current session

POST

/external-webhook-accounts

POST

/external-webhook-account-find

Look up an existing webhook account

POST

/external-webhook-account-tags

Manage tags on a webhook account

POST

/external-webhook/{webhookType}

POST

/login

Authenticate and receive a bearer token

POST

/logout

Invalidate the current session

POST

/external-webhook-accounts

POST

/external-webhook-account-find

Look up an existing webhook account

POST

/external-webhook-account-tags

Manage tags on a webhook account

Why though Jentic?

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

Credential isolation

MotionOps login credentials are stored encrypted in the Jentic vault (MAXsystem). Agents call /login through Jentic and receive only the short-lived bearer token; the username and password never enter agent context.

Intent-based discovery

Agents search Jentic with intents like 'register a MotionOps webhook' and Jentic returns the matching operation across the 9 endpoints with its input schema, so the agent can register a handler without consulting docs.

Time to first call

Direct MotionOps integration: half a day to wire login plus webhook registration. Through Jentic: minutes — search, load, execute the two calls in sequence.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Routific API

Routific solves vehicle routing for the jobs MotionOps schedules.

Pair with MotionOps when the agent needs optimised driving routes for technicians dispatched out of MotionOps.

Alternative

Track-POD API

Track-POD is another field operations platform with stronger proof-of-delivery focus.

Choose Track-POD when the agent needs proof-of-delivery and route execution; choose MotionOps for field-service job and account management.

Complementary

Slack API

Slack receives MotionOps webhook events relayed to a team channel.

Pair with MotionOps when the agent needs to post incoming job-update webhooks to a Slack channel.

FAQs

Specific to using MotionOps API API through Jentic.

Why is there no official OpenAPI spec for MotionOps API?

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

MotionOps uses bearer-token authentication. POST credentials to /login to receive a token, then attach it as a Bearer header on the webhook endpoints. Through Jentic, the login credentials sit in the encrypted vault and only the issued token reaches the agent.

Can I receive job events from MotionOps via webhooks?

Yes. Register an external webhook account via /external-webhook-accounts, then register a handler URL for each event type via /external-webhook/{webhookType}. MotionOps will POST to those URLs when matching events occur.

What are the rate limits for the MotionOps API?

MotionOps does not publish hard rate limits in the spec. Cache the bearer token from /login for its lifetime and avoid re-authenticating on every webhook write.

How do I register a webhook through Jentic?

Run pip install jentic, search 'register a MotionOps external webhook', load /external-webhook-accounts, then load /external-webhook/{webhookType} and execute both. Jentic supplies the bearer token from your vault.

Is the MotionOps API free?

API access is included with a MotionOps subscription. There is no separate API tier; pricing is per workspace on the MotionOps platform.