> ## Documentation Index
> Fetch the complete documentation index at: https://developers.openborder.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrate OpenBorder Shipping Labels with ShipHero WMS

> Connect OpenBorder's label generation to ShipHero WMS using ShipHero's Generate Label Webhook to automatically sync labels into your fulfillment center.

If your fulfillment center uses ShipHero as its WMS, you can sync OpenBorder shipping labels directly into ShipHero using ShipHero's Generate Label Webhook. This integration eliminates the need for manual label retrieval and ensures labels are available in ShipHero as soon as they are generated.

## Prerequisites

Before starting the setup, confirm the following:

* Your fulfillment center (FC) uses ShipHero as its WMS.
* You have an FC code provided by the OpenBorder team.
* You have access to configure webhooks in your ShipHero instance, or you are able to request this from your ShipHero account representative.

## How It Works

ShipHero supports external label providers through its Generate Label Webhook mechanism:

* ShipHero's Generate Label Webhook allows external label providers to be registered against a ShipHero account.
* Once configured, ShipHero automatically calls the OpenBorder label endpoint whenever a label is needed for an order — no manual API calls are required from your side.
* The endpoint OpenBorder exposes for this integration is:
  ```text theme={null} theme={null}
  POST /fc/labels/shiphero/{fc_code}
  ```
  where `{fc_code}` is the unique fulfillment center identifier provided to you by the OpenBorder team.

## Setup Steps

<Steps>
  <Step title="Get Your FC Code">
    Contact the OpenBorder team to receive your `fc_code` identifier. This code is unique to your fulfillment center and is required as part of the ShipHero endpoint URL. Keep it available for the steps that follow.
  </Step>

  <Step title="Share Credentials with OpenBorder">
    Provide the OpenBorder team with the following credentials from your ShipHero account:

    * **Shared secret** — found in your ShipHero app settings.
    * **API key** — found in the ShipHero Request Verification section of your ShipHero configuration.

    OpenBorder uses these credentials to authenticate incoming webhook requests from ShipHero, ensuring that only legitimate ShipHero requests are processed.

    <Note>
      The OpenBorder team needs your ShipHero shared secret and API key to authenticate webhook requests between ShipHero and OpenBorder. Contact your account manager to provide these securely.
    </Note>
  </Step>

  <Step title="Configure ShipHero">
    Ask ShipHero support or your ShipHero account representative to register the OpenBorder endpoint as a Generate Label Webhook on your account.

    Provide them with the following endpoint URL, substituting your actual `fc_code`:

    ```text theme={null} theme={null}
    POST /fc/labels/shiphero/{fc_code}
    ```

    Once registered, ShipHero will call this endpoint automatically whenever a label needs to be generated for an order processed through your fulfillment center.
  </Step>

  <Step title="Test the Integration">
    Create a test order that flows through ShipHero and verify the following:

    1. ShipHero calls the OpenBorder endpoint automatically when the order requires a label.
    2. The label is generated by OpenBorder and synced back into ShipHero.
    3. The label appears correctly against the order in ShipHero and is ready to print.

    If the label does not appear, check that your `fc_code` is correct in the endpoint URL and confirm with the OpenBorder team that your ShipHero credentials were received and configured successfully.
  </Step>
</Steps>

## Next Steps

* [Webhooks Guide](/guides/webhooks) — Understand how OpenBorder delivers label results asynchronously and how to verify webhook payloads.
* [Get Label API Reference](/api-reference/shipping-labels/get-label) — Explore the underlying label endpoint for additional context on request and response formats.