SimpliRoute integration
SimpliRoute is a last-mile delivery and route planning platform. Create, read, update and delete visits (deliveries and pickups) and their items, list visits by date, check out visits and trigger recipient notifications, create plans and routes, start routes, manage vehicles, the client master, users (drivers), couriers, route properties, webhooks and, with the Accounting add-on, invoices, delivery issues and products, and list skills, tags, zones, fleets, sellers and observations. Not covered: the route optimization API and the TMS and datamart APIs (other hosts), the GPS feed, picture uploads, webhook listing (it returns stored header values) and the full-replacement updates of visits, vehicles and route properties (their partial updates are offered) and of users. Authentication is the account API token, sent as Authorization: Token <token>.
Say what should happen.
The workflow builds itself.
What you can do with SimpliRoute
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Courier, 6 operations
create_courierCreate courierPOSTCreates a courier (delivery company or person) or a fleet provider; trade_name must be unique among active couriers. Courier add-on and admin token needed.create_courier_visitsCreate courier visitsPOSTCreates visits and has couriers assigned to them in the background (courier add-on): pass visits, a list of visit objects. Returns the visits without the assignment; get_visit shows it later.delete_courierDelete courierDELETEDeletes a courier (courier add-on, admin token).get_courierGet courierGETReturns one courier or fleet provider (courier add-on, admin token).list_couriersList couriersGETLists the active couriers and fleet providers of the account (courier add-on, admin token): names, contacts, tax id, reference and provider_type.update_courierUpdate courierPUTUpdates a courier with the fields you send and returns it; the reference example sends two fields and keeps the others. Courier add-on and admin token needed.
Vehicle, 6 operations
create_vehicleCreate vehiclePOSTCreates a vehicle (name, capacities, start and end locations, skills, shift, rest time, extra properties) and returns it.delete_vehicleDelete vehicleDELETEDeletes a vehicle.get_vehicleGet vehicleGETReturns one vehicle with capacities, depots, skills, shifts and status; include_extra_properties=true adds your own properties.list_vehiclesList vehiclesGETLists the vehicles of the account with capacities, depots, skills, shifts, rest times and status; include_extra_properties=true adds your own properties.list_vehicles_with_routesList vehicles with routesGETLists the vehicles that have routes on a date (YYYY-MM-DD), each with its driver and its route and plan ids; a vehicle can have several routes in a day.update_vehicleUpdate vehiclePATCHChanges only the fields you send on a vehicle and returns it. extra_properties are merged: listed ones are created or updated, one sent as null is deleted.
Visit, 6 operations
create_visitsCreate visitsPOSTCreates one or more visits (deliveries, pickups or service orders): pass visits, a list of visit objects with title, address and planned_date required. Returns the created visits with ids and tracking ids.delete_visitDelete visitDELETEDeletes a visit. Removing a visit from a route already built does not recalculate the arrival times of the following stops.delete_visitsDelete visitsPOSTDeletes several visits at once: pass visits, the list of visit ids. The reference does not describe the answer.get_visitGet visitGETReturns one visit with its status, time windows, contact (personal data), loads, checkout data, signature and picture URLs, and items.list_plan_visitsList plan visitsGETLists the visits of the routes of a plan with status, order, route_id and checkout time. The reference titles it visits by route, but its path takes the plan id and its example lists two routes.update_visitUpdate visitPATCHChanges only the fields you send on a visit and returns the visit. A change does not recompute the arrival times of the other stops of a route already built.
Client, 4 operations
create_clientsCreate clientsPOSTCreates one or more clients in the client master: pass clients, a list of objects with key, title and address. Returns the created clients.delete_clientDelete clientDELETEDeletes a client from the client master.list_clientsList clientsGETLists the clients of the client master (addresses, time windows, contacts as personal data, skills, tags); pass key to find one client by your own key.update_clientsUpdate clientsPUTUpdates clients of the client master: pass clients, each with its id. The reference does not say whether fields left out are kept: read the client with list_clients and send all its fields back.
Driver, 4 operations
create_usersCreate usersPOSTCreates one or more user accounts (drivers and other roles) with their login password: pass users, a list of objects with username and password. Returns the users without passwords.delete_userDelete userDELETEDeletes a user account.get_userGet userGETReturns one user: username, name, phone and email (personal data), role flags and last login.list_usersList usersGETLists the users of the account (drivers and other roles): id, username, name, phone and email (personal data), role flags and last login.
Invoice, 4 operations
create_invoiceCreate invoicePOSTCreates an invoice (bill, credit note, delivery note or debit note) for a visit; needs the Accounting add-on. reference, currency, visit and type are required.delete_invoiceDelete invoiceDELETEDeletes an invoice (Accounting add-on).get_invoiceGet invoiceGETReturns one invoice (Accounting add-on): reference, currency, visit, type, payment method and payments, status, items, delivery issue and label.update_invoiceUpdate invoicePATCHChanges the fields you send on an invoice (Accounting add-on); an invalid or empty currency is replaced by the account country currency.
Routes property, 4 operations
create_route_propertiesCreate route propertiesPOSTCreates the properties of a route (color, is_start_blocked). Fails if the route already has properties: use update_route_properties then.delete_route_propertiesDelete route propertiesDELETEDeletes all the properties of a route (its color and start block).get_route_propertiesGet route propertiesGETReturns the properties of a route: its color and whether its start is blocked.update_route_propertiesUpdate route propertiesPATCHChanges only the properties you send on a route (color, is_start_blocked) and returns them.
Delivery issue, 3 operations
create_delivery_issueCreate delivery issuePOSTCreates a delivery issue (a reason for non-delivery or a problem at delivery) usable on invoices or items (Accounting add-on).delete_delivery_issueDelete delivery issueDELETEDeletes a delivery issue (Accounting add-on).update_delivery_issueUpdate delivery issuePATCHChanges the fields you send on a delivery issue (Accounting add-on).
Product, 3 operations
create_productsCreate productsPOSTCreates one or more products that invoice items can refer to (Accounting add-on): pass products, a list of objects with title and sku.delete_productDelete productDELETEDeletes a product (Accounting add-on).update_productUpdate productPATCHChanges the fields you send on a product (title, sku, price) (Accounting add-on).
Webhook, 3 operations
create_webhookCreate webhookPOSTSubscribes a URL to an event: SimpliRoute POSTs the event JSON there with the headers you set, expects HTTP 200 and retries 3 times within 120 s. It documents no signature. Stored values are not returned.delete_webhookDelete webhookDELETEDeletes the webhook of an event (webhook names the event, for example route_started).update_webhookUpdate webhookPUTReplaces the URL and headers of the webhook of an event. Stored values are not returned.
Item, 2 operations
add_invoice_itemsAdd invoice itemsPOSTAdds items to an invoice (Accounting add-on): pass items, a list of objects with title and reference required, optional sku, unit_price, planned_units, delivered_units, type, product.add_visit_itemsAdd visit itemsPOSTAdds one or more items to an existing visit: pass items, a list of objects with title and optional load, load_2, load_3, reference, notes, quantity_planned, status.
Route, 2 operations
create_routeCreate routePOSTCreates an empty route for a vehicle and a driver on a date, inside a plan (plan id from create_plan), with start and end locations and estimated times. Returns the route.update_route_referenceUpdate route referencePATCHSets the reference field of a route (your own label, for example a customer name) and returns the route.
Bulk search, 1 operation
search_route_propertiesSearch route propertiesPOSTReturns the properties (color, is_start_blocked) of several routes in one call: pass route_ids.
Checkout, 1 operation
checkout_visitCheckout visitPOSTRegisters the checkout of a visit as completed, failed or pending, with time and position, as a driver would in the app: this changes the delivery record. Notifications are sent separately by notify_visits_checkout.
Client property, 1 operation
create_client_propertyCreate client propertyPOSTCreates a client custom property (label, type str, int, float or bool) that clients can then carry in custom_properties. The reference does not describe the answer.
Create plan, 1 operation
create_planCreate planPOSTCreates a plan for one day (unique name, start_date equal to end_date), empty or with routes, each with driver, vehicle, times and visits. Returns the plan and its route ids.
Detail, 1 operation
get_visit_detailGet visit detailGETReturns the detail of a visit: driver and vehicle names, checkout time, comment and user, pictures, signature, extra field values, items, pickup items and invoices.
Extra field, 1 operation
list_extra_fieldsList extra fieldsGETLists the extra fields of the account (custom checkout form fields): id, label, key, type, options and flags. Use their key with set_visits_extra_field_values.
Extra field value, 1 operation
set_visits_extra_field_valuesSet visits extra field valuesPOSTStores extra field values on visits: json is a JSON-encoded object of extra field key (from list_extra_fields) to value, visits the visit ids; every listed visit gets the same values.
Fleet, 1 operation
list_fleetsList fleetsGETLists the fleets of the account (needs the Fleet module): name, vehicle ids and user ids of each fleet.
Notify, 1 operation
notify_visits_checkoutNotify visits checkoutPOSTSends the checkout notifications (SMS, WhatsApp, email and live tracking) for the visits listed: real messages go to their recipients. Call it after checkout_visit.
Observation, 1 operation
list_observationsList observationsGETLists the checkout observations of the account: the customizable reasons recorded when a visit is completed or failed (id, type, label).
Paginated, 1 operation
list_visitsList visitsGETLists the visits of one date (planned_date) or a range of up to 30 days (start_date, end_date) with their full activity, up to 500 per page: raise page until next is null.
Register, 1 operation
start_routeStart routePOSTRegisters the start of a route: send type ROUTE_STARTED, the route_id and date_time. SimpliRoute records the start time and updates the visits arrival estimates.
Seller, 1 operation
list_sellersList sellersGETLists the sellers of the account (id, name, alias, language); the feature must be activated by SimpliRoute.
Skill, 1 operation
list_skillsList skillsGETLists the skills of the account (id, name): constraints matching visits to vehicles, for example a visit requiring COLD needs a vehicle with COLD.
Tag, 1 operation
list_tagsList tagsGETLists the visit tags of the account (id, label, color); tags are created by SimpliRoute support and shown to drivers in the mobile app.
Zone, 1 operation
list_zonesList zonesGETLists the zones of the account (needs the Zones module): name, polygon coordinates, assigned vehicle ids, enabled flag and active days.
Use SimpliRoute from Claude Code, Cursor or Codex
Connect SimpliRoute in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SimpliRoute operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect SimpliRoute
- Create your workspace
Sign up free. Nothing to install.
- Connect SimpliRoute once
Add your SimpliRoute connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
SimpliRoute integration FAQ
What can you do with the SimpliRoute integration?
LiveContext exposes 63 operations on SimpliRoute, covering courier, vehicle, visit and client.
