Connector library

Implemented source Commerce, Finance & Operations APIs

ShipStation connector.

Look up ShipStation v2 shipment status and routing metadata, find shipments modified in a time window, and inspect connected carrier summaries.

Connector download

Download ShipStation

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.1 Choose version
Release
2026-10-03
Package
Implemented source
Schema credentials
Bearer token
Connection settings
API Base URL
Package size
9 KB
SHA-256
ac1e9596e4fb5b4ede9f36deab89caa38d4cd2e55d6d17cc705538e7da1c58fa

Version history

What's new

  1. v0.2.0.1Latest · 2026-10-03 · Implemented source

    Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.

  2. v0.2.0.0Earlier · 2026-10-03 · Implemented source

    Look up ShipStation v2 shipment status and routing metadata, find shipments modified in a time window, and inspect connected carrier summaries.

  3. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Retained immutable historical scaffold archive.

Included in this version

Included actions

Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.

Get shipment

Retrieve selected status, dates and routing IDs for one v2 shipment.

Find shipments

Return one page of shipment summaries modified in a required time window.

Get carrier

Retrieve selected identity, connection and billing-plan flags for one connected carrier.

List carriers

Return one page of connected carrier summaries without financial or extended service data.

Vendor API

API and access

Implementation considerations
  • Confirm whether the customer needs order reads, order creation, inventory, refunds, fulfillment, or marketplace-specific behavior.
  • Use external IDs, order IDs, fulfillment IDs, and payment IDs to avoid duplicate work during retries.
  • For broad commerce APIs, start with get/search/create/update order, customer, product, and fulfillment actions.

Support

Need help with ShipStation?

Tell us what you need to connect or change.