Skip to main content Skip to complementary content
Already have an account? Sign in

ShipHero (v1)

Last updated: 9/15/2026

ShipHero integration summary

Stitch’s ShipHero integration replicates data using the ShipHero API (v1.2). Refer to the Schema section for a list of objects available for replication.

ShipHero feature snapshot

A high-level look at Stitch's ShipHero (v1) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Released on March 8, 2019

Supported by

Singer Community

Stitch plan

Standard

API availability

Available

Singer GitHub repository

singer-io/tap-shiphero

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Supported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Supported

Column selection

Supported

Select all

Supported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting ShipHero

Step 1: Generate a ShipHero API token

  1. Sign into your ShipHero account.
  2. Using the top menu in ShipHero, click My Account > Settings > API.
  3. On the API Credentials page, click into the Shop Name field and enter the name of the shop you want to use.
  4. Click the Add button to generate the API credentials.

The API Key on this page is what you’ll need to complete the setup in Stitch.

Step 2: Add ShipHero as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the ShipHero icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch ShipHero” would create a schema called stitch_shiphero in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the ShipHero Token field, paste the value from the API Key field in ShipHero.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your ShipHero integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond ShipHero’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

ShipHero integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 5: Set objects to replicate

The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

For ShipHero integrations, you can select:

  1. Individual tables and columns

  2. All tables and columns

Click the tabs to view instructions for each selection method.

  1. In the integration’s Tables to Replicate tab, locate a table you want to replicate.
  2. To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.

  3. To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.

  4. Repeat this process for all the tables and columns you want to replicate.
  5. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
  1. Click into the integration from the Stitch Dashboard page.
  2. Click the Tables to Replicate tab.

  3. In the list of tables, click the box next to the Table Names column.
  4. In the menu that displays, click Track all Tables and Fields:

    The Track all Tables and Fields menu in the Tables to Replicate tab
    The Track all Tables and Fields menu in the Tables to Replicate tab

  5. Click the Finalize Your Selections button at the bottom of the page to save your data selections.

Initial and historical replication jobs

After you finish setting up ShipHero, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

ShipHero table reference

orders

The orders table contains info about the orders in your ShipHero account.

Replication Method

Key-based Incremental

Primary Key

id

Useful links

orders schema on GitHub

ShipHero API method

products

The products table contains info about the products in your ShipHero account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

products schema on GitHub

ShipHero API method

shipments

The shipments table contains info about the shipments in your ShipHero account.

Replication Method

Key-based Incremental

Primary Key

shipment_id

Useful links

shipments schema on GitHub

ShipHero API method

vendors

The vendors table contains info about the vendors in your ShipHero account.

Replication Method

Full Table

Primary Key

vendor_id

Useful links

vendors schema on GitHub

ShipHero API method

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!