Skip to main content

Prerequisites

Before continuing, you should have already completed the following for this connector:
1

Configure the Connector

Enable the connector and set up its connector profile in your project. See Managing Connectors.
https://stackone-logos.com/api/orderspace/filled/png

Connector Profile

Orderspace - OAuth 2.0
2

Link an Account

Connect an account using StackOne Hub or Auth Link.
https://stackone-logos.com/api/orderspace/filled/png

Link Account

Orderspace - OAuth 2.0

Subscribe via the StackOne dashboard

This connector uses Programmatic Webhooks. When you enable webhook events for a connected Orderspace account, StackOne automatically registers a single webhook subscription in Orderspace (via POST /v1/webhooks) pointing at the StackOne Native Webhook URL, subscribed to all the events you selected.

1

Select event subscriptions in the dashboard

In the StackOne dashboard, open the Orderspace connector profile and enable the webhook events you want to receive. See the Available Webhook Events section below for the full list.

2

Connect the Orderspace account

On account connection (or when event subscriptions change), StackOne registers the webhook in Orderspace on your behalf using the connected account’s OAuth2 credentials. One consolidated subscription covers all selected events.

3

Verify delivery

Trigger a matching change in Orderspace (for example, create a test order) and confirm the event reaches your downstream consumer.

  • Orderspace sends events as an HTTP POST to the StackOne endpoint; StackOne responds with 200 OK automatically.
  • If Orderspace receives any other response it retries with an incremental backoff, and disables the webhook after multiple failed attempts.
4

Unsubscribe

Changing your event selection re-registers the subscription with the updated event list. Disconnecting the account deletes the StackOne-managed webhook from Orderspace, stopping all deliveries.

Available Webhook Events

The following Orderspace events can be enabled. Only events selected in StackOne are included in the subscription — Orderspace will not deliver events that are not subscribed.

1

Customer events

Events related to customer companies on the account.

  • Customer Created (customer.created) — Fired when a new customer company is added
  • Customer Updated (customer.updated) — Fired when an existing customer record changes
  • Customer Deleted (customer.deleted) — Fired when a customer is deleted
2

Order and dispatch events

Events related to orders and dispatches.

  • Order Created (order.created) — Fired when a new order is placed
  • Order Updated (order.updated) — Fired when an existing order changes
  • Order Deleted (order.deleted) — Fired when an order is deleted
  • Dispatch Created (dispatch.created) — Fired when items on an order are dispatched
3

Invoice and payment events

Events related to invoicing and payments.

  • Invoice Created (invoice.created) — Fired when an invoice is created
  • Invoice Deleted (invoice.deleted) — Fired when an invoice is deleted
  • Payment Created (payment.created) — Fired when a payment is made or recorded against an invoice
4

Product and inventory events

Events related to the product catalog and stock levels.

  • Product Created (product.created) — Fired when a new product is created
  • Product Updated (product.updated) — Fired when an existing product changes
  • Product Deleted (product.deleted) — Fired when a product is deleted
  • Inventory Level Updated (inventory_level.updated) — Fired when a SKU’s stock level changes. Bulk stock changes produce one event per SKU

Delivery format and security

Details of how Orderspace delivers events to StackOne.

1

Batched payloads

The payload of each request is a list of events. A request usually contains a single event, but Orderspace may batch multiple events into one request (up to 50) to reduce network traffic — most commonly on bulk actions such as stock updates. StackOne routes each delivery to the matching event handler.

2

Delivery security

Delivery to StackOne is authenticated by the unique token embedded in the Native Webhook URL. The token is generated per connected account and validated on every incoming request, so only requests sent to your account’s registered URL are accepted.

Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.