Platform/11/Integrations and APIs
11 Integrations and APIs
The systems you already pay for, made to agree.
Most dealer groups do not need one more system. They need the ones they have to agree with each other. Every platform on this page is integrated and operated in production: pulled on a schedule, signed where it can be, verified before it is trusted, and counted every run so a partial failure raises an alert instead of under-reporting in silence.
/ Works with
01 The surface
Twenty-nine platforms,
filtered by what they do.
Hover any platform for what the integration actually does.
All product names, logos, and brands are the property of their respective owners, and are used here to identify the platforms myEZData integrates with. Their appearance does not imply any partnership, sponsorship, or endorsement.
02 Carrier and point of sale
The feeds that were never
designed to be feeds.
Carrier statements and scorecards
Statements, scorecard exports, mobile-internet lines, retention cohorts and post-date reports are imported on schedule with multi-field dedup keys and reconciled to the store master by door code, never by name.
Point of sale collectors
Forty-seven collectors run against the point of sale and the carrier portals on a fleet managed and monitored from the landlord panel: credentials per dealer, schedules, last run, last error, and a job that tells you when a collector silently returns nothing.
Workforce and traffic
Two-way schedule and timesheet sync with ConnectTeam where a dealer keeps it, and door-traffic sensors feeding conversion reports with a watchdog that files a ticket when a door goes quiet.
03 Partner API
Signed both ways,
counted every run.
Sample responses. Note the webhook: an invalid signature is rejected, which is the whole point of signing it.
| Direction | What | How |
|---|---|---|
| Pull, every 20 minutes | Catalog, warehouse inventory, store inventory on order, orders with line items, ship notices | Signed requests: a user header and an HMAC of the request path with a shared secret. Delta-aware, one shot, with a received count and a partial-failure alert per run. |
| Push, from the supplier | Shipping events | Inbound webhook verified against a separate secret before the payload is trusted. A staging mode logs and skips writes. |
| Outbound, from us | Approved orders, live inventory checks | A separate endpoint and key. Orders placed with the supplier get the supplier's order number written back. |
| Read API, for partners | Shipments, catalog, orders | Partner keys stored as hashes with an eight-character prefix, per-key scopes, request counts and an optional IP allow-list. |
| Finance | Remittance file, receivables, aging | Payment files imported by header names and keyed on the supplier's order number; a weekly tripwire on aging. |
Rows are tenant-resolved per store on our side: the supplier only knows a door code, and the master dealer never holds partner data.
04 Shipping, money and identity
UPS
Inbound device purchase orders tracked per store through the carrier's alert webhook and a tracking poller. We issue the OAuth token the carrier's webhook client presents; only the vendors that warrant it get the paid alert subscription.
Plaid and the bank
Linked accounts pull posted transactions for reconciliation; a CSV upload covers banks without a link. Transactions first, a resumable cursor, and master accounts skipped.
Stripe and ADP
Per-location subscription billing across four tiers reconciled to webhooks, and the payroll provider's register matched to the calculated run.
Microsoft Entra ID and Graph
Sign in with Microsoft across every dealer subdomain, account provisioning from onboarding, and outbound mail from the dealer's real mailbox.
Push and messaging
One push pipeline for Android and iOS, WhatsApp cards through a per-dealer gateway, inbound email into tickets, voice through Twilio.
Identity verification and maps
Veriff for onboarding identity checks, Google Maps for the directory, the field map and the geofence coordinates.
05 Automation
105 scheduled jobs,
each one reporting on itself.
Gates and kill switches
Every partner job is gated on its credentials and a hold switch, so a feed can be paused without unscheduling it. A health monitor and a scheduler audit catch the job that silently skips.
Received counts
Each pull logs a run id and how many rows it received. Zero where there should be hundreds is an alert, not a quiet Tuesday.
Integration config
Credentials and switches per dealer group live on the landlord panel; the dealer's own panel shows what is connected and when it last ran.
06 Related
Security and tenancy
Entra ID sign-in, a database per dealer group, layered permissions, immutable records.
/ 04Reconciliation
Bank and armored cash, refunds and rebates, carrier statements, supplier receivables.
/ 05Store operations
Store detail, orders center, inbound device tracking, inventory, visits and audits.
/ allEvery platform page
The twelve deep dives, one per capability, with the overview above them.
→ Start
Tell us what you
already pay for.
Carrier, POS, bank, supplier, payroll, identity. We tell you which are already connected, which take a week, and which we would not touch.
Request a demo