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

Security and fleet isolation

Design the receiving application around a fixed authorized fleet context. The credential identifies that context; caller-supplied company or fleet identifiers cannot expand it.

Server-side boundary

  • Every request authenticates the key or supported OAuth token and checks current account/fleet eligibility.
  • Individual reads and summaries are scoped to the credential's fleet and its current exclusive ownership. Ambiguous ownership is denied.
  • Related driver and vehicle registry IDs are resolved only inside the same fleet; ambiguous matches are null.
  • Snapshot cursors are authenticated and bound to their user, fleet and query. Snapshot contents are encrypted and also carry their bound authorization context.
  • Snapshot continuation rechecks access and withholds source rows that have been deleted, moved or made private.
  • Release 0.2 drive lists and drive summaries exclude private and unknown drive classes.

This describes the intended and tested boundary of this release, not a guarantee about an unverified deployment. Check release status. Receiving systems must apply their own access controls after data has been delivered.

Receiving-service responsibilities

Store keys in a backend secret store. Fix the API origin in configuration, verify TLS normally and refuse redirects carrying credentials. Do not expose a general URL-fetch function based on source text.

Separate customers' credentials, queues, stored data, caches and application permissions. Never cache a response under a date range alone: include the authorized tenant/fleet context. Do not allow one customer's staff to select another customer's credential.

Treat descriptions, labels, job references and addresses as untrusted data. Escape them when rendering HTML and protect spreadsheet exports against formula injection. Never execute source text or interpret it as instructions.

Logs, retention and support

Avoid logging keys, raw Authorization headers, full source payloads or unnecessary personal data. Record operational outcomes with your own correlation identifiers instead.

Set retention and access policies for addresses, driver identifiers and other personal data. Revoking an Ewooks key prevents future reads; it cannot remove data already copied into your systems.

For an access or suspected isolation issue, stop the affected integration, revoke its key through the fleet owner, and contact your established Ewooks support channel. Share environment, time, tool and a sanitized correlation reference, never the key or another customer's data.

Public documentation

This site contains synthetic examples and public interface information only. It neither requests an API key nor calls the data API from your browser. Search runs against this site's static index; it does not send your search to an external service.

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