Commerce

An API your customers can build against.

The Customer Pricing API gives your customers programmatic access to their Zigaflow account. Their developers can pull customer-specific pricing, submit orders, raise RFQs that create quotes in their account, and subscribe to webhooks for real-time event notifications - building customer-facing portals and internal tools straight against your data.

Partner API3 active connectionsCONNECTED PARTNERSAcme CorpProducts · Orders · InventoryLast sync2 min agoManage accessTradePack LtdProducts · Catalogue syncLast sync14 min agoManage accessNova SuppliesPending: awaiting first syncStatusConfiguringView setupAPI CREDENTIALS - ACME CORPAPI Keyzf_live_••••••••••••••••abc4CopyRevokeAUDIT LOG09:14:22 GET /products 200 OK · 09:14:05 POST /orders 201 Created · 09:13:48 GET /stock 200 OKFull audit log of every API call with timestamp
4

core capabilities: pricing, orders, RFQs and event webhooks

Real-time

pricing responses and webhook event notifications

Per-customer

credentials scoped to that customer's own data

What is it?

Let your customers integrate Zigaflow into their own systems

The Customer Pricing API is a programmatic interface that gives your customers direct access to their Zigaflow account. Their developers can build customer-facing applications, internal procurement tools, or website integrations that work with their specific catalogue and pricing - without manual data entry or back-and-forth with your team.

The API supports four core capabilities: retrieve customer-specific pricing, submit orders, submit RFQs that create quotes inside the customer's Zigaflow account, and subscribe to webhooks for real-time event notifications such as order status changes.

Access is scoped to the customer's own data. Each customer receives their own credentials and can only interact with their own pricing, orders, and quotes. You enable API access, share the credentials and documentation, and the customer's development team handles the integration from there.

The Customer Pricing API is built for customers who want to embed Zigaflow into the systems they already use - whether that's a procurement portal, an internal ordering tool, or a customer-facing website that needs live pricing, ordering, and quote requests.

What you can do
Retrieve customer-specific pricing in real time
Submit orders programmatically via the API
Submit RFQs that create quotes in the customer's Zigaflow account
Subscribe to webhooks for order status changes and other events
Scoped credentials - customers only see their own data
JSON over HTTPS using standard REST patterns
Live, account-accurate pricing on every API call
Built for customer developers building integrations
Common problems

Sound familiar?

01

Your customers want to integrate, but you don't have the engineers

The problem
Your customers' developers want to pull live pricing, submit orders, raise RFQs, and react to status changes from inside their own systems - procurement portals, internal ordering tools, or customer-facing websites. But building and maintaining a public-facing API requires engineering resource most SMBs don't have in-house. Hiring a developer for a one-off build is expensive and slow, and without ongoing technical resource, the integration becomes brittle. Customer relationships that could be running on clean automation stay stuck on manual email and spreadsheet exchange.

How Zigaflow fixes it
The Customer Pricing API is a managed API layer Zigaflow runs on your behalf. You enable it from inside your account, generate credentials for each customer, and share them alongside the documentation. Your customer's developers connect using standard REST patterns - retrieving customer-specific pricing, submitting orders, raising RFQs that create quotes in their Zigaflow account, and subscribing to webhooks for real-time event notifications. Zigaflow handles all the infrastructure, so there is no engineering overhead on your side.
Developer Required to OpenPartnersystemwants toconnectNo developerWithout a developer the connection never gets built
02

Customers who want API access are choosing suppliers who offer it

The problem
In markets where procurement teams increasingly expect API connectivity, businesses that can offer programmatic pricing and ordering win deals that businesses without it lose. If a customer is choosing between you and a competitor, and the competitor lets their developers pull live pricing and submit orders via API, that is a real commercial disadvantage with nothing to do with the products themselves. Technical connectivity is becoming part of the buying decision.

How Zigaflow fixes it
The Customer Pricing API gives you the same connectivity larger, more technically resourced suppliers offer - without their engineering team. Your customers' developers get clean credentials, documented endpoints, real-time pricing, order submission, RFQs that become quotes in their account, and webhooks for order status changes and other events. You become a supplier that is easy to integrate against, which is a meaningful differentiator when customers are evaluating options.
PartnerchoosingCompetitorAPI enabledConnect in hoursAutomated syncReal-time updatesPartner chooses themYouNo APIEmail onlyManual transferDelayed updatesPartner goes elsewhere
03

Giving customers programmatic access raises security and audit questions

The problem
Letting external customers' systems talk directly to your data is a security responsibility. Without proper tooling, the options are bad: share login credentials, build bespoke endpoints per customer, or refuse access entirely. Any of those make it hard to audit who is doing what, hard to revoke access when a relationship changes, and easy to give a customer more access than they need. Treating customer integration as an ad-hoc exception rather than a managed capability creates risk that scales with every new customer you onboard.

How Zigaflow fixes it
The Customer Pricing API uses purpose-built credential management. Each customer receives their own credentials scoped only to their own pricing, orders, and quotes - they cannot see or interact with any other customer's data. Credentials are revoked instantly from your admin panel if a relationship changes. Every API call - pricing lookups, order submissions, RFQ submissions, webhook deliveries - is logged with a timestamp and credential identifier, giving you a clear audit trail of what each customer has accessed and when.
Your ZigaflowAccount and dataPartner Apassword123 (shared)Full access ⚠Partner Bpassword123 (same!)Sees A's data ⚠Partner CRelationship endedStill has access ⚠Partner DDifferent password?Nobody knows ⚠No audit trail. No revocation. No access control.
How it works

From setup to results in minutes

1

Enable the Customer Pricing API

Navigate to Customer Pricing API in your Zigaflow account settings and enable the feature. Your account immediately has an active API endpoint ready to accept customer connections. Zigaflow generates base API documentation automatically, covering the endpoints available based on your account configuration - pricing lookups, order submission, RFQ submission, and webhook subscription. No technical setup is required on your side - enabling the feature is all that is needed to make your account API-accessible to credentialed customers.

2

Create Credentials for Each Customer

For each customer you want to give API access to, create a set of API credentials from the Customer Pricing API management panel. Assign a name for internal reference, define the permissions - what their developers can read and what actions they can take - and generate the key and secret. Zigaflow creates a unique credential pair per customer, ensuring access is isolated to that customer's own data and revoking one customer has no effect on any others.

3

Share Credentials and Documentation

Send your customer their API credentials and a link to the endpoint documentation. Zigaflow provides standard API documentation covering authentication, available endpoints, request formats, and response structures - your customer's developers have everything they need to build the integration from their side. You are not involved in the technical work; you provide access and the customer's development team handles the implementation against the four available capabilities: customer-specific pricing, order submission, RFQ submission, and event webhooks.

4

Your Customer's Developers Build the Connection

Your customer's development team uses the credentials and documentation you have shared to build the integration from their system to Zigaflow - retrieving pricing, submitting orders, raising RFQs that create quotes in their Zigaflow account, and subscribing to webhooks for event notifications. You do not need to be involved in the technical work. Once the customer confirms their integration is ready, run a brief test to verify data is flowing correctly before marking the connection as live. Zigaflow's support team can help troubleshoot if anything does not behave as expected.

5

Monitor and Manage Customer Access

From your Zigaflow Customer Pricing API dashboard, view connection activity for each customer - when they last connected, what actions were taken, and any errors. Rotate credentials at any time without disrupting other customers. If a customer relationship ends, revoke their credentials instantly from the same panel - no developer action required on your side and no residual access to your account remains.

Common questions

Frequently asked

Ready to get started? Try it free.

14-day free trial on all plans. No credit card required.

Start free trialBook a demo