AI Implementation Prompts

Use these prompts with an implementation agent or vendor team. Replace bracketed values before sending.

Connector Service

Build a production TypeScript connector service for Fleet Core. Read vehicles,
drivers, GPS, CAN, and tachograph download results from [VENDOR SYSTEM]. Push
data to Fleet Core using signed HMAC HTTP ingest. Implement stable external IDs,
local sync cursors, exponential backoff for 429 and 5xx, no retries for 401 or
403, and tests for signature generation, payload mapping, idempotency, and
retry behavior.

Admin API Client

Build a Fleet Core admin API client. Implement login, refresh, logout, GET
/auth/me, customer context selection, Authorization bearer headers,
X-Customer-Id, optional X-Reseller-Id, pagination, 401 refresh-and-retry, and
typed helpers for customers, users, vehicles, devices, telemetry, reports, and
connectors.

Auth Integration

Implement Fleet Core auth in [APPLICATION]. Store access tokens only in memory,
store refresh tokens in the platform's secure credential store, refresh once on
401, require explicit customer selection when multiple active memberships exist,
and surface 403 errors as permission or tenant mismatch errors.

Troubleshooting

Given this Fleet Core request, response, headers, and payload, diagnose whether
the failure is auth, tenant scope, permission, HMAC signing, validation,
idempotency, or upstream availability. Provide the smallest next test and a
fixed curl command.