API & EDI
API Authentication
Every Flxpoint API request must be authenticated with an access token passed as a bearer token in the Authorization header. Flxpoint issues separate, context-scoped tokens for Sources, Channels, and Resellers (B2B); this page covers each token type, how to generate and send it, and how to resolve 401 errors.
Claude MCP Connector Setup and Workflows
Connect your Flxpoint account to Claude AI via OAuth to analyze orders, purchase orders, and invoices using natural language tools and pre-built workflow prompts.
Integrating to FLX EDI
A quick orientation to Flxpoint EDI (X12 EDI over SFTP) (supported transactions, SFTP basics, and getting started) that bridges to the dedicated EDI Help Center for the full, always-current spec.
Webhooks
Flxpoint webhooks send an HTTPS POST to a URL you configure whenever a subscribed event occurs, optionally scoped to a single source or channel, so your systems can react to events like a fulfillment request entering processing.
XML Integration
XML is a structured, text-based format Flxpoint uses to exchange product, inventory, pricing, and order data, either through scheduled FTP file feeds or live API responses, with each field mapped to a matching Flxpoint field.