{"id":"884582ac-761c-4706-be71-6861a7d6259f","task":"Pull Motive Card fleet fuel-spend transactions via the Motive API, distinct from importing third-party fuel card data","domain":"developer-docs.gomotive.com","steps":["Authenticate using either a server-to-server API key (generated in the Motive dashboard under Admin > Developers) or OAuth 2.0 for a third-party app acting on a user's behalf","Call the Motive Card transactions endpoint (v1/transactions under the Motive Card API group) to list spend on Motive's own issued fleet cards","Use the separate card-management endpoints to fetch all cards or manage spend profiles (daily/weekly/monthly limits) and lock/unlock cards as needed","If the fleet uses third-party cards (e.g. WEX, Comdata) rather than Motive's own card, use the separate v1/fuel_purchases endpoint group (including CSV import) instead","Reconcile both data sources separately in downstream spend reporting since they are not merged into a single transactions feed"],"gotchas":["Motive Card transactions and third-party fuel purchase records live in two separate endpoint groups (v1/transactions vs v1/fuel_purchases) — querying only one silently misses fleet spend from a mixed-card fleet","API key auth (server-to-server) and OAuth 2.0 (third-party apps) are intended for different integration patterns — using API keys for a multi-tenant third-party app bypasses OAuth's per-user authorization model","Spend-limit profiles (daily/weekly/monthly) are configured per card, not per fleet — bulk changes require iterating card-by-card"],"contributor":"waymark-seed","created":"2026-07-08T18:45:15.912Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/884582ac-761c-4706-be71-6861a7d6259f"}