Endpoints shaped exactly like the real services.
The point of a native adapter is that there's nothing to adapt. Your existing QuickBooks/Stripe/Plaid integration code points at Fictix and just works.
Why 'shaped like' beats 'a generic API'
A generic test API forces you to write a translation layer you then have to trust. Fictix instead answers in the exact response shape of each real service— QuickBooks looks like QuickBooks, Stripe like Stripe — so the code path you test is the code path you ship. Zero adapter code, zero “works against the mock, breaks against prod.”
What's covered
~20 services answer with native-shaped endpoints today:
| Category | Services |
|---|---|
| Accounting | QuickBooks Online, Xero, NetSuite, Sage Intacct |
| Payments | Stripe, Square, Brex, Mercury |
| Banking | Plaid, Chase |
| Payroll / HR | Gusto |
| CRM / Commerce | HubSpot, Shopify |
| Productivity / Office | Slack, Asana, Airtable, Gmail, Outlook, Google Drive, OneDrive, Excel, DocuSign |
Additional services have execute-only handlers (schema + execution, no full native surface yet). The set grows; the contract — native shape, no adapter — does not change.
How you point at it
Each project gets service-scoped endpoints. Internally:
# native, service-shaped
GET /api/v1/orgs/{slug}/native/qbo/v3/company/{id}/query
GET /api/v1/orgs/{slug}/native/stripe/v1/charges
GET /api/v1/orgs/{slug}/native/plaid/transactions/get
# external staging handoff (one URL to your integration)
https://staging.fictix.dev/{project}/qbo/v3/...
https://staging.fictix.dev/{project}/stripe/v1/...Swap your base URL, keep your client library and auth flow. The shapes, pagination, and IDs behave like the real API's.
One company, every system, all coherent
The adapters aren't independent fakes. A charge in the Stripe surface is the same economic event as the invoice in the QuickBooks surface and the deposit in the Plaid surface — one company's truth, projected into each API's shape. That cross-system coherence is the thing isolated sandboxes can never give you.
Questions
Do I need to rewrite my integration to test against Fictix?
No. Endpoints mirror each real service's response shape, so you change the base URL and keep your existing client code, auth, and parsing.
Which services are supported?
~20 native-shaped today across accounting (QuickBooks, Xero, NetSuite, Sage Intacct), payments (Stripe, Square, Brex, Mercury), banking (Plaid, Chase), payroll (Gusto), CRM/commerce (HubSpot, Shopify), and office tools; more have execute-only handlers.
Is data consistent across services?
Yes — every service surface projects the same underlying company, so the Stripe charge, the QuickBooks invoice, and the Plaid deposit are the same event.