GSMTasks Project API

Name: GSMTasks Project API
Brand: GSMTasks Project API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceShipping LogisticsapiKey261 EndpointsREST

For Agents

Manage delivery tasks, routes, route optimisation jobs, drivers, vehicles, and webhooks in GSMtasks for last-mile and fleet operations.

Install Jentic One Beta

Connect the GSMTasks Project API to your agent

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

Create, list, retrieve, update, and cancel delivery tasks across the GSMtasks workspace

Manage drivers (workers), vehicles, and account roles to keep the dispatch pool current

Trigger route optimisation jobs and read the resulting routes for a fleet on a given day

GET STARTED

Start building with GSMTasks Project API

Explore with Jentic

View OpenAPI Document

The GSMtasks API is a RESTful service for last-mile delivery, task dispatch, and route optimisation. It exposes 261 endpoints covering accounts, account roles, tasks, orders, routes, route optimisation jobs, drivers (workers), vehicles, customers, documents, payments, webhooks, integrations, and reporting. Authentication is by an Authorization header containing an API token, and the API is the integration surface used by delivery operators, logistics platforms, and fleet managers to wire GSMtasks into their wider stack. Resources are heavily CRUD-shaped, and most collections support filtering, pagination, and PATCH for partial updates.

Use Cases

Patterns agents use GSMTasks Project API for, with concrete tasks.

★ Last-mile delivery dispatch

Create and dispatch last-mile delivery tasks from an e-commerce or warehouse system into GSMtasks, then track them through completion. The integration creates tasks via the tasks endpoints, assigns them to drivers, and optionally triggers route optimisation so a day's tasks are sequenced efficiently. Webhook subscriptions push status events back into the source system so the warehouse always knows which orders are on the road and which are delivered.

When an order is ready, create a GSMtasks task with the delivery address and assignee, then poll the task status until it reaches completed.

Route optimisation pipeline

Run a daily route optimisation job over the next day's task list so drivers start their shift with sequenced stops rather than ad-hoc routes. The agent pushes the day's tasks into GSMtasks, triggers a route optimisation request, and reads the resulting routes back to display in the driver app. This pattern shaves miles and minutes off each shift, particularly for operators with 10+ drivers.

Trigger a route optimisation job for tomorrow's tasks and then retrieve the resulting routes for each driver.

Driver and fleet roster sync

Keep the GSMtasks roster of drivers (workers), vehicles, and account roles in sync with an HR or fleet-management system of record. The integration creates and updates GSMtasks account_roles when staff change, and updates vehicle records when registrations or capacities change, so dispatch never assigns work to an off-duty driver or the wrong vehicle. Activate and notify endpoints make onboarding and re-activation explicit operations rather than data hacks.

When the HR system reports a new driver, create the matching GSMtasks account_role and call its activate endpoint.

AI agent integration through Jentic

Expose GSMtasks operations to a logistics agent through Jentic so dispatchers can ask things like 'show me unassigned tasks for tomorrow' or 'reroute driver 12 around traffic'. The agent searches Jentic for the right intent, loads the operation schema, and executes it against api.gsmtasks.com. Jentic stores the GSMtasks Authorization token in its vault, so the agent only sees a Jentic-mediated session, not the raw token.

Through Jentic, search 'create a GSMtasks task', load the operation, and execute it for the order being dispatched.

Key Endpoints

261 endpoints — the gsmtasks api is a restful service for last-mile delivery, task dispatch, and route optimisation.

METHOD

PATH

DESCRIPTION

GET

/account_roles/

List drivers and account roles

POST

/account_roles/

Create a new driver or account role

POST

/account_roles/{id}/activate/

Activate an inactive account role

GET

/accounts/{id}/

Retrieve a tenant account

PATCH

/accounts/{id}/

Partially update a tenant account

POST

/accounts/{id}/stripe_create_setup_intent/

Create a Stripe setup intent for billing

POST

/accounts/{id}/change_owner/

Change the owner of an account

GET

/account_roles/

List drivers and account roles

POST

/account_roles/

Create a new driver or account role

POST

/account_roles/{id}/activate/

Activate an inactive account role

GET

/accounts/{id}/

Retrieve a tenant account

PATCH

/accounts/{id}/

Partially update a tenant account

Why Jentic?

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

Credential isolation

The GSMtasks Authorization token is stored encrypted in the Jentic vault. Agents call the API through Jentic and receive scoped Jentic agent keys (ak_*); the raw GSMtasks token never enters the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'create a delivery task' or 'trigger route optimisation' and Jentic returns the matching GSMtasks operation schema with required body and path parameters ready to execute.

Time to first call

Direct GSMtasks integration with a 261-endpoint surface: 1-2 weeks to wire up the tasks, routes, account_roles, and webhook flows end-to-end. Through Jentic: a few hours once the token is vaulted, because each agent intent maps to a single search-load-execute call.

FAQs

Specific to using GSMTasks Project API through Jentic.

What authentication does the GSMTasks API use?

GSMTasks uses an apiKey-style token in the Authorization header (the spec calls the scheme tokenAuth). Tokens are issued in the GSMtasks dashboard. Through Jentic the token is stored encrypted in the vault and the agent only authenticates to Jentic with a scoped agent key (ak_*).

Can I trigger route optimisation programmatically?

Yes. GSMtasks exposes route and route-optimisation endpoints that accept the day's tasks and return optimised stop sequences. Combined with the tasks list endpoints this is enough to run a fully automated daily routing pipeline without using the GSMtasks web UI.

What are the rate limits for the GSMTasks API?

The published spec does not document explicit rate limits. GSMtasks throttles at the platform level per tenant; back off on HTTP 429 responses and prefer webhooks over polling for high-frequency status checks.

How do I create a delivery task through Jentic?

Install Jentic with pip install jentic, search for 'create a GSMtasks task', load the matching operation, and execute it with the customer, address, and assignee fields. Jentic resolves the call to the GSMtasks tasks create endpoint and returns the new task id for tracking.

Can I subscribe to task status events?

Yes. GSMtasks exposes webhook endpoints so the platform pushes events to your endpoint when task or route state changes. This avoids polling 261 endpoints for changes and keeps the source system close to real time.

How do I keep the driver roster in sync with my HR system?

Use the account_roles endpoints. Create roles for new drivers via POST /account_roles/, update them with PATCH /account_roles/{id}/, and call POST /account_roles/{id}/activate/ when an inactive driver returns to duty. PATCH calls are partial so you only need to send the fields that changed.

GSMTasks Project API

Connect the GSMTasks Project API to your agent

Capabilities

Start building with GSMTasks Project API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs