allGeo API

Name: allGeo API
Brand: allGeo API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementbearer12 EndpointsREST

For Agents

Manage work orders, job sites, devices, and time clock entries for a field workforce, and send messages to deployed workers via the allGeo API.

Install Jentic One Beta

Connect the allGeo API to your agent

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

Authenticate with login and refresh tokens for tenant-scoped access

Create or update work orders for scheduled field jobs

Provision new job sites and remove ones no longer in service

GET STARTED

Start building with allGeo API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for allGeo API, keeping it validated and agent-ready. allGeo is a workforce management platform for distributed and field teams, and the API covers work orders, job sites, devices, time clock entries, and SMS or push messaging. Authentication is bearer-token based with explicit login and refresh endpoints, and the API is scoped to operational data — not payroll calculation or invoicing. The endpoint set is small enough to learn in a session yet covers the core daily operational events of a field workforce.

Use Cases

Patterns agents use allGeo API for, with concrete tasks.

★ Field service scheduling

Dispatch teams push new work orders into allGeo whenever a customer ticket is approved, then update or delete them as plans change. POST /api/v1/schedule creates or updates a work order in one call, and DELETE /api/v1/deleteSchedule/{workOrderNumber} removes one. The flat endpoint shape avoids juggling multiple resource trees per dispatch event.

Call POST /api/v1/schedule for work order WO-9123 with the technician ID, job site name, and start time, then verify the response indicates success.

Mobile time clock capture

Operations capture clock-in and clock-out events from the allGeo mobile app via POST /api/v1/createTimeClock and update them via POST /api/v1/updateTimeClock. The data feeds downstream payroll without manual sheet collection. This is the fastest path to enforce attendance accuracy in distributed teams.

Record a clock-in for employee E-101 at job site 'Warehouse-3' by calling POST /api/v1/createTimeClock with the timestamp.

Field crew messaging

Coordinators push job updates to workers via allGeo's messaging endpoint, which dispatches an SMS or push notification depending on device registration. POST /api/v1/allgeo/sendMessage takes the worker identifier and the body, and the message lands on the device the worker uses in the field. This avoids a separate SMS provider integration when allGeo is already in place.

Send an SMS to worker E-204 with body 'Reschedule: arrive at site Warehouse-3 at 14:00' via POST /api/v1/allgeo/sendMessage.

AI agent dispatch automation

An AI agent watching customer tickets can create the matching allGeo work order, register the assigned device, and message the technician in one chained execution. Through Jentic the agent searches by intent for each step and the bearer token never appears in the prompt. This converts a manual dispatch console into an event-driven loop.

Use Jentic to search 'create an allGeo work order', execute POST /api/v1/schedule with the ticket data, then call POST /api/v1/allgeo/sendMessage to alert the technician.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/react/v1/login

Authenticate and obtain a bearer token

GET

/react/v1/refresh

Refresh an expired bearer token

POST

/api/v1/schedule

Create or update a work order

POST

/api/v1/createSites

Create a job site

POST

/api/v1/createDevices

POST

/api/v1/createTimeClock

Record a time clock entry

POST

/api/v1/allgeo/sendMessage

Send SMS or push notification

POST

/react/v1/login

Authenticate and obtain a bearer token

GET

/react/v1/refresh

Refresh an expired bearer token

POST

/api/v1/schedule

Create or update a work order

POST

/api/v1/createSites

Create a job site

POST

/api/v1/createDevices

Why Jentic?

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

Credential isolation

allGeo bearer tokens are stored encrypted in the Jentic vault, with login and refresh handled inside the execution layer. Agents never see the raw token in their prompt context.

Intent-based discovery

Agents search 'create an allGeo work order' and Jentic returns POST /api/v1/schedule with its input schema, so the agent supplies dispatch fields without reading the docs.

Time to first call

Direct allGeo integration: 1-2 days for login, refresh handling, and resource-specific request shapes. Through Jentic: under 1 hour — search, load, execute.

FAQs

Specific to using allGeo API through Jentic.

Why is there no official OpenAPI spec for allGeo API?

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

Bearer token, obtained by calling POST /react/v1/login and refreshed via GET /react/v1/refresh. Through Jentic, the token is held in the encrypted vault and injected at execution time so it never appears in agent prompts.

Can I create or update a work order with the allGeo API?

Yes. POST /api/v1/schedule creates or updates a work order in one call, and DELETE /api/v1/deleteSchedule/{workOrderNumber} removes one. This is the primary dispatch surface for the API.

How do I record a time clock entry via the allGeo API through Jentic?

Run pip install jentic, search 'record a time clock entry in allGeo', load the input schema for POST /api/v1/createTimeClock, and execute with the worker ID and timestamp.

Can the allGeo API send messages to workers?

Yes. POST /api/v1/allgeo/sendMessage dispatches an SMS or push notification to a registered worker, removing the need for a separate SMS provider when allGeo is the system of record for the field workforce.

Does the allGeo API handle payroll calculation?

No. The API captures time clock events and operational data but does not run payroll. Use a payroll API such as Gusto or BambooHR for net pay calculation, deductions, and pay stubs.

allGeo API

Connect the allGeo API to your agent

Capabilities

Start building with allGeo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs