eewooksdevelopers
Release 0.2 documentationAPI 0.2.0 is live and verified. Check availability before integrating.

Data lifecycle and financial use

The MCP API gives your program recorded fleet data. Your integration remains responsible for deciding which records and quantities may be sent to another business system.

Keep three quantities separate

  1. Recorded distance: the stored mileage-log value.
  2. Reimbursable distance: the distance approved for an employee's reimbursement.
  3. Billable distance: the distance approved for a customer's work order or invoice.

These quantities can differ. The API does not derive the latter two from the first, assign payroll categories, decide vehicle-ownership rules, or create billing rows.

Completion and approval

A record being saved, or having an end time, does not prove that a manager has checked it. This release has no API approval state or approval event. Establish a separate, auditable approval step in the receiving workflow before payroll or invoicing.

work_id is a free-text reference. Validate that it identifies the correct work order in the target system. A day with several jobs can require several separately reviewed assignments; do not infer those assignments from a daily total.

Source identity and duplicate prevention

Use (environment, fleet_id, resource type, id) as the source-record identity. Persist the downstream record reference, the accepted source values, the purpose of the transfer and its result.

Do not use an address, timestamp, driver name or distance as a unique transfer key. Do not treat a JSON-RPC request id as an event ID; it only correlates a request and response.

If a downstream write times out, determine whether it committed before retrying. Use the receiving system's idempotency or lookup mechanism where available. Re-reading a source record must not automatically create a second payroll or billing entry.

Corrections and deletions

This release does not offer a modification timestamp filter, monotonically increasing revision, tombstones, change feed or webhooks. The record id stays the same across ordinary edits and is not a version counter.

Repeated bounded reads can help reconcile an agreed open period, but they do not guarantee detection of every historic edit or deletion. A record can move outside the queried date range or become unavailable because of authorization or privacy changes. Never automatically delete financial entries merely because a row is absent from a later read.

For the first integration, prefer explicitly approved export periods/batches and a documented manual correction process. If continuous authoritative change synchronization is required, arrange that capability with Ewooks before relying on it in production.

Target-system adapters

The API is independent of the receiving system. The receiving developer must arrange its write interface, identifier mappings, payroll/billing categories and correction rules. These docs do not promise an existing Ultima, Ecom or other accounting-system connector.

Ewooks Developer Documentation · Updated 21 November 2026 · Synthetic examples only