Custom commerce API
Tell us about an existing merchant API that exposes structured products, variants, pricing or availability.
Custom Store / API
Request accessYour commerce stack does not have to fit a standard connector.
If your store runs on a custom platform, private commerce API or another structured source, submit an integration request so the Chatout team can review the data, authentication and workflow requirements.
Custom integration request
Merchant commerce source
Store
Demo Fashion API Store
Source type
Custom commerce API
Data needed
Products · variants · pricing · inventory
Review before implementation
Chatout reviews the source, authentication model and required commerce fields before a custom connector path is approved.
Built for non-standard stores
Start with the commerce source your business already owns.
The goal is not to copy changing product facts into AI prompts. Chatout needs a structured merchant source that can be reviewed and integrated behind a controlled connector boundary.
Private store platform
Request support for an internal or proprietary commerce system that does not use a standard Chatout connector.
Structured catalog source
Describe the structured commerce source your business already maintains so the integration path can be reviewed.
Controlled integration
Custom access is reviewed before commerce data becomes part of the Chatout sales workflow.
Request flow
Request first. Review the source. Define the connector.
Custom integrations are reviewed instead of being activated automatically because every proprietary commerce system can expose different authentication, product models and availability rules.
Submit the request
01Tell Chatout what store or commerce source you use and what business data the integration needs.
Review the requirements
02The source, authentication model, available fields and required sales workflow are reviewed.
Define the integration path
03If the source is suitable, the connector requirements and authoritative commerce fields can be defined.
Use approved data only
04Customer-visible commerce answers should rely only on validated fields exposed through the approved connector.
Source priority
Structured commerce data beats public website guesses.
Public website content can provide useful context, but it should not become the authority for live stock, variant availability or other changing commerce facts.
1
Live commerce API
Preferred when current structured commerce data is available.
2
Structured commerce feed
Useful when an approved structured source is available without a live API.
3
Public website
Can provide reference context, but should not be treated as authoritative live inventory.
4
Merchant knowledge
Useful for policies and guidance such as shipping, returns and FAQs.
Integration boundaries
A custom connector should not become unrestricted AI access.
Even with a custom commerce source, Chatout should use approved backend interfaces and validated structured results before customer-visible messages are produced.
Credentials stay behind the backend integration boundary.
Customer-visible price and stock should come from approved structured data.
The AI should not invent unsupported commerce fields when the source cannot provide them.
Workspace and tenant authorization remains enforced for custom integration data.
Chatout remains a sales automation layer, not a buyer payment gateway.
Clear expectations
A request is not an instant connector.
Custom Store / API requests require review. Submitting a request does not mean the source is immediately supported or that every field exposed by the merchant system will automatically be available to Chatout.
Request
Merchant submits source details
Status
Reviewed by Chatout
Implementation
Defined after approval
Commerce truth
Only approved structured fields
Custom commerce
Tell us where your commerce data lives.
Create your Chatout workspace and submit a Custom Store / API request so the integration requirements can be reviewed.