Connect Overstock: pull orders in, push fulfillment out

Take the API base URL and API key from your Overstock partner integration docs, paste them into Integration, test, map, activate — orders flow in and fulfillment flows back.

The Overstock connector pulls orders from Overstock — now operating as the Bed Bath & Beyond platform — into OMS, and pushes fulfillment back to the platform. It can also push product and inventory updates out, so orders, shipping, and stock stay in sync on both sides.

Prerequisites#

• An Overstock partner account selling on the platform now branded Bed Bath & Beyond.
• Your Overstock partner integration docs. The API base URL and the endpoint paths come from those docs — Overstock has no public REST API spec, so nothing about the endpoints can be checked anywhere else.
• The partner API key issued for your account, as described in those same partner integration docs. Have it ready to copy — you will paste it into Integration, not type it from memory.

Get your credentials#

1. Open the Overstock partner integration docs for your account. Both values you need — the API base URL and the API key — are taken from those docs; there is no public REST API spec to look them up in instead.
2. In those docs, find the API root URL and copy it exactly. This is the value for the API base URL field — it starts with https://. Copy the root URL as written in the docs, and confirm the endpoint paths against the same docs.
3. In the same docs, find your partner API key and copy it. Keep it somewhere safe: it is a secret, it is sent as the x-api-key header on every request, and Integration never echoes it back after you save.

Fill it into Integration#

1. Open Integration → Connector Marketplace → Overstock → New connection.
2. API base URL (required): paste the API root URL you copied from your Overstock partner integration docs, in the form https://… . Paste the root URL from the docs as it is — do not type in the platform storefront address, and do not guess an address: Overstock has no public REST API spec, so the docs are the only source for this value.
3. API key (required): paste the partner API key from the same docs. It is sent as the x-api-key header, is encrypted at rest, and is never echoed back — after saving, the field will not show the key again, so keep your own copy from the docs.

Test the connection#

Click Test connection. The test uses your API base URL and sends your API key as the x-api-key header to check connectivity, then shows a document-level preview with one real order, platform fields next to the standard order. If your account has no orders yet, the connectivity check can still pass — wait for or arrange one real order before judging the preview, and see the FAQ below if the test fails.

Mapping / pick a template#

Pick the Overstock standard template. It maps order number, line SKUs, quantities, and ship-to address into the standard order, and maps fulfillment back into platform format. Check the mapping preview before activating, especially that each platform SKU is paired to the right product, so product and inventory pushes report the right items.

Activate#

After activation, Integration pulls new Overstock orders on the schedule you set, and pushes fulfillment with tracking, plus product and inventory updates, back to the platform. Watch the first few orders in Runs / Logs before trusting it unattended.

FAQ#

Test fails: the API key is rejected

The API key is wrong. Every request carries the key as the x-api-key header, so a key copied with a character missing, a key from a different account, or a value that is not the partner API key at all will be rejected at the first call — the base URL never even gets a chance to matter.

Go back to your Overstock partner integration docs, copy the partner API key again from there, replace the API key value in the connection, save, and test again. Paste it — do not retype it.

Test fails: the platform cannot be reached at the API base URL

The API base URL is filled in wrong. The field needs the API root URL from your partner integration docs; the platform storefront address, a page address copied from a browser, or a guessed address all point somewhere the API does not answer. Because Overstock has no public REST API spec, a URL that looks plausible can still be wrong — only the docs define the right one, endpoint paths included.

Open your partner integration docs, copy the API root URL again exactly as written, replace the API base URL in the connection, and confirm the endpoint paths against the same docs. Save and test again.

Connected but no orders come in

The connection itself is fine — testing passes — but the platform has no new orders for your account yet, so there is nothing to pull. A working connection with an empty order list looks exactly like this until the next order is placed.

Wait for the next real order on the platform, then run a manual pull and check Runs / Logs. New orders appear once the platform has issued them — if orders exist on the platform and still do not appear after a manual pull, re-check the API base URL and API key against your partner integration docs first.