What are you building?
Pick a starting point. We'll skip you past the parts that don't apply, then the assistant (bottom-right) handles the questions in plain English.
I'm building a Channel
Marketplace, storefront, or POS
Flxpoint pushes you product data; you publish on your surface and send orders back.
- Channel token (scoped, own rate-limit bucket)
- Core endpoints: Listing, Order, Shipment
I'm building a Source
Supplier, warehouse, or 3PL
Flxpoint pulls inventory from you and routes fulfillment requests your way.
- Source token (scoped to one source)
- Core endpoints: Inventory, Fulfillment Request, Shipment
I just need to read data
Reporting, BI, internal tooling
Poll Flxpoint for orders, inventory, or shipments to surface elsewhere.
- Account token (broadest read scope)
- Filter by date. Never pull the full set
I'm migrating from v1
Old integration to update
v1 is retired. v2 is the same shape with a renamed auth header and a few endpoint moves.
- Base URL: api.flxpoint.com (no /v1)
- Auth header: X-API-TOKEN
Already know what you need? Skip the guides and browse all 233 endpoints.
Not sure? Ask the assistant (bottom-right).
Or browse by category
Jump into a resource
Top 8 by operation count. Full list in the reference.
Routed dropship orders. Accept, ship, and update tracking back to Flxpoint.
Per-channel listings published from master products. Push and sync state.
Master catalog. Create, read, and update product records and variants.
Carriers, services, and rates that drive routing decisions.
POs to suppliers — create, receive, and reconcile against inventory.
Rules that compose master products from incoming source feeds.
Automations that fire on order, inventory, and listing events.
Stock levels by source and SKU. Push updates, fetch availability.
Describe what you're building.
Tell us in one sentence what you're trying to do. We'll pick the handful of endpoints you actually need and tell you why.