Set up Posbytz

Push Zopping orders to Posbytz. Orders placed in Zopping are sent to the Posbytz /orders API and updates via PUT /orders/{posbytzOrderId}. This is a built-in connector — register your API host and access token.

Prerequisite: the ThirdPartyIntegration extension must be enabled for the organization.

1. Configure credentials

Add your Posbytz details to the organization's integration config under the POSBYTZ key:

{
  "partnerIntegration": {
    "partnerCredentials": {
      "POSBYTZ": {
        "baseURL": "https://api.posbytz.com",
        "accessToken": "<oauth-access-token>"
      }
    }
  }
}

Field	Required	Notes
`baseURL`	yes	Your Posbytz API host. Zopping appends paths like `/orders` and `/orders/{posbytzOrderId}`.
`accessToken`	yes	OAuth access token. Sent in the `Authorization: Bearer <token>` header.

2. Supported events

Direction: PUSH = Zopping → Posbytz.

Direction	Events
PUSH	`ORDER_CREATE`, `ORDER_COMPLETE`, `ORDER_CANCEL`

Enable delivery per event via event integrations.

Mapping notes

Before pushing an order, Zopping expects these keys in the order's metaData: posbytzCartId, posbytzAddressId, posbytzPaymentMethodId, and (for updates) posbytzOrderId.
Order type PICKUP is sent as pickup; everything else as delivery.

Going further

Integrations overview · Events & webhooks