enerkad.net

What It Is

Robonobo Planner API is the companion API for the Robonobo Planner app. It is designed to let businesses automatically push delivery, pickup/drop-off, or customer on-site service tasks into the system, avoiding manual entry of customer names, addresses, and other details in the back office. Once created, destinations can be passed to couriers or technicians for handling in the Robonobo Planner app.

Core Capabilities

Based on the documentation, it offers a fairly complete REST API: you can create a single destination or create destinations in bulk, with up to 1000 records per request. It also supports creating paired collecte/livraison tasks—pickup and delivery records linked by the same customerReference. For queries, you can look up destinations by internal id or customerReference, as well as retrieve pickup/delivery pairs and destination lists. Supported fields cover address, city, postal code, latitude/longitude, phone number, notes, weight, declared value, email, time windows, service duration, custom dynamicFields, and multiLevelRef for multi-level parcel/pallet references.

API and Documentation

Authentication uses a two-step process: first call getauthtoken with Basic credentials to obtain a token, then call business endpoints with a Bearer Token. Token TTL can also be configured. The documentation includes cURL examples, JSON requests/responses, and field descriptions, so integration should not be too difficult for developers. Fields such as EventHistory, driver location, signature URL, photo URL, trackingUrl, and labelUrl also show that it covers the fulfillment tracking flow. However, the main documentation does not appear to mention SDKs, webhooks, rate limits, versioning, or a complete error-code system, so engineering-related information is still somewhat limited.

Pricing and Deployment

The documentation does not disclose pricing, plans, free quotas, or payment methods. It only states that users need to create an account at robonoboplanner.fr and then create an API account in the settings. It also does not specify whether the product is open source, self-hostable, or available for private deployment. The API uses api.robonoboplanner.fr, which suggests a SaaS-style integration, but this cannot be confirmed from that alone.

Pros, Cons, and Who It Is For

Its strengths are that the business fields are closely aligned with logistics scenarios, with support for bulk imports, pickup/delivery workflows, status history, real-time tracking, and dynamic fields. It is suitable for teams with existing order management, warehouse/distribution, or field-service ticketing systems that want to automate integration. The downsides are that the documentation is in French, which may increase the learning cost for international teams, and there is limited information on commercial terms, support, ecosystem integrations, and SDKs.

Access from China

The documentation does not mention availability, payment, or compliance for mainland China, so these remain unknown. If the target scenario is local delivery in China, it may also be worth evaluating route-planning capabilities from Amap or Baidu Maps, or international alternatives such as Onfleet, Routific, and OptimoRoute.