RFP Essential Knowledge: Integrations and APIs
Essential knowledgeCore knowledge to understand Fluent Commerce
Author:
Michael Wholohan
Changed on:
29 May 2026
Overview
Fluent Commerce is an API-first, event-driven platform. All business capabilities are exposed via APIs, enabling 100% interoperability with backend, third-party, and headless front-end systems. The platform supports GraphQL, REST, webhooks, and event-based integration patterns, with a growing library of pre-built connectors and an extensible Connect SDK for building custom integrations.Key points
- Intended Audience: Developer, Solution Architect, Integration Engineer
- Classification: Integrations and APIs
GraphQL and REST APIs
GraphQL is the primary and recommended integration endpoint for Fluent Commerce.- Fluent provides a rich catalogue of 200+ objects available for query and mutation over a JSON-based GraphQL API endpoint.
- GraphQL is a single endpoint — no versioned URL changes. Backward compatibility is a core architectural principle.
- API response times typically fall below 1,000ms. Exact response times vary depending on object type and result set size.
- Platform availability SLA: **99.95% per month.
API documentation:
- GraphQL: https://api.production.shared-sydney-01.fluentcommerce.com/graphql/docs/
- Authentication API: https://docs.fluentcommerce.com/essential-knowledge/authentication-api
- REST Event API: https://docs.fluentcommerce.com/essential-knowledge/event-api
Authentication: All APIs require a time-bound bearer token (24-hour expiry) obtained via an OAuth flow.
REST APIs: A set of legacy REST-based APIs remain available for specific use cases. Batch inventory upload is available via REST as an alternative to real-time GraphQL delta feeds.
Third-party Connectors
Fluent provides certified, pre-built connectors for common commerce platforms and services:Pre-built Connectors:
- Salesforce Commerce Cloud - Native connector
- Salesforce Service Cloud - Certified cartridge
- Adobe Commerce (Magento)- Native connector
- CommerceTools - Native connector
- Kafka - Connect SDK connector
- Adyen - Pre-built adaptor (iPaaS partnership)
- CyberSource - Pre-built adaptor (iPaaS partnership)
Drop ship vendors (DSV): Fluent can push and receive triggers from DSV platforms via webhooks and API. A Connect SDK connector accelerates integration work for new DSV onboarding.
EDI: Fluent does not natively support EDI data exchange. EDI integration should be handled via an integration layer/middleware.
SFTP and batch integration: Supported for specific legacy use cases via the integration layer, with SFTP connectors and middleware for automated, scheduled data exchange.
Webhooks and Events
Fluent is built on an event-driven architecture. Every action within the platform generates an event:- Events are broad in nature, contain standard and custom categorisations, and can be subscribed to over API.
- Events are filterable and can be used to drive monitoring, reporting, and third-party system triggers.
- Webhook outbound calls can be configured to trigger at any point during the order lifecycle.
- All events and logs can be exported to third-party analytics and monitoring tools (e.g. Dynatrace, Datadog, Grafana, EFK).
Audit logging: All access to client data is logged — capturing who performed the action, what was acted on, when, and the result. See [Information Security](./02-information-security.md) for full audit log specifications.
Rate limiting: Application constraints are in place to prevent throttling of underlying AWS service calls. Standard platform usage limits apply per hour per account (see [Infrastructure and Hosting]
Salesforce Integration
Fluent has specific depth of integration with the Salesforce ecosystem:- Salesforce Commerce Cloud — native certified connector for order and inventory data synchronisation.
- Salesforce Service Cloud — certified cartridge for case management. The pre-built connector includes native Live Chat capability.
For return label retrieval, Fluent can trigger a call to an integrated CMS from within Fluent Store or OMX via API.
Integration Best Practices
- Orders should be sent to Fluent via an integration layer or ESB rather than directly from the order capture channel.
- Data validation, cleansing, and deduplication should be handled upstream in middleware before reaching Fluent.
- For mass data extraction or initial load, use GraphQL queries or contact the Fluent SRE team for bulk data extraction support. See [Bulk Extracts with GraphQL](https://docs.fluentcommerce.com/by-type/bulk-extracts-with-graphql).
- For BI and analytics integration, Fluent has been successfully integrated with Tableau, Snowflake, QuickSight, Google Data Studio, and Cyfe. Fluent does not provide standard connectors to BI tools — GraphQL and Event APIs are used to feed dashboards directly.
