Data & Storage · Integration
Mac Centre API
Add Mac Centre API to your product for your customers, and give your AI agents governed access to it.
Embed a Mac Centre API integration so your product can read the sales documents a customer's back office already holds, rather than keeping a copy that drifts. The connector is read oriented: sales orders, sales invoices and sales shipments can be fetched one at a time when a user opens a record, or paged through in batches for a first load. Each customer connects their own account, so every read is scoped to that tenant, and pagination and throttling are handled for you so a backfill does not exhaust their allowance. fastn owns the credentials and API upkeep, and the same governed connection gives your AI agents scoped, audited read access.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own account so their sales orders, invoices and shipments can be read inside your product.
Look up a single order, invoice or shipment when a user opens a record, instead of maintaining a copy of it.
Page through orders and invoices in batches for a first load, with pagination and rate limits handled for you.
Keep every read scoped to the tenant that authorised it, so no customer sees another's sales documents.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers where an order stands by reading that customer's own order and shipment records.
An agent reconciles an invoice against the order behind it, with each read audited.
An agent lists a customer's recent orders and explains which are not yet shipped.
Example prompt
Look up this order and tell me whether it has been invoiced and shipped.
Set up Mac Centre API in 4 steps
- 01Enable the Mac Centre API connector in your fastn dashboard.
- 02Have each customer supply their own credentials so reads run under their account.
- 03Map the order, invoice and shipment fields your product displays.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Mac Centre API integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Mac Centre API integration without building it. Your customers connect their own Mac Centre API account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Mac Centre API update is not your on-call problem.
- One integration serves your product and your agents. The same governed Mac Centre API connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Works well with
NetSuite
Exact Online
InvoicedOften used alongside
Tools the same teams tend to run next to Mac Centre API, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceMac Centre API integration FAQ
How do I add a Mac Centre API integration to my product?
Enable the Mac Centre API connector in your fastn dashboard, then let each customer authenticate their own Mac Centre API account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Mac Centre API client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Mac Centre API account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Mac Centre API account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Mac Centre API integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent answers where an order stands by reading that customer's own order and shipment records.
Who maintains the Mac Centre API integration?
fastn does. When Mac Centre API changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Mac Centre API integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Mac Centre API reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Mac Centre API integration?
A common starting point: let each customer connect their own account so their sales orders, invoices and shipments can be read inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Mac Centre API integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Mac Centre API does not change your per-connector cost. You can start free with 3 connected accounts.
Add Mac Centre API to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.