Contents

Connection

Check that your API key works and see which company it belongs to and what it can read.

Getting a key. In Nucleo, go to Commerce › Orders › Channels and logistics, click New connection and choose Integration (Commerce API) under Integrations. The endpoint, the API key (nck_…) and the webhook secret (whsec_…) are shown once: keep them in your secret store. A new connection is a draft and answers 403 connection_not_active: in its Status, choose Active and save. Rotate credentials in the connection's More actions replaces the key and the webhook secret; the old ones stop working at once. A new key can use every read scope below; orders:write is never given by default: ask Nucleo support to enable it on your key.

ScopeOpens
orders:readOrders, with shipments, refunds and timeline
returns:readReturns, with outcome and refunds
inventory:readAvailability per item and location
locations:readWarehouses and stores
orders:writeCreate orders (POST /orders) — only on request

Base URL, authentication and conventions of this API are on the Commerce API page.

get/ping

Check your API key

The company and connection your key belongs to, the scopes it has (orders:write only when enabled) and the webhooks it receives. Needs no scope.

GET https://api-commerce.nucleoplatform.com/api/commerce/v1/ping
Authentication: Bearer token
Rate limit: 600 requests per 1m, per connection — Default limit; ask Nucleo support if you need another one.

Responses

  • 200The key works.
    Headers
    • X-Request-Id The id of this call. Quote it if you contact support; errors repeat it as request_id.
    • api_versionstringrequired
    • companyobjectrequired
      Child attributes
      • idinteger
      • namestring | null
    • connectionobjectrequired
      Child attributes
      • idstring
      • namestring
      • statusstring
    • scopesarray of stringrequired
      One oforders:readreturns:readinventory:readlocations:readorders:write
    • webhooksobjectrequired
      Child attributes
      • enabledbooleanrequired

        A webhook URL is set and the key has a webhook secret. A key created before webhooks existed has no secret: rotate its credentials to get one.

      • eventsarray of stringrequired

        The events this key receives (empty when webhooks are off).

        One oforder.createdorder.status_changedshipment.shippedreturn.createdreturn.status_changed
    • server_timestring (date-time)required
  • 401unauthorized: the key is missing or wrong, or the call comes from an IP outside the connection's allowlist.
    Headers
    • X-Request-Id The id of this call. Quote it if you contact support; errors repeat it as request_id.
    • errorobjectrequired
      Child attributes
      • codestringrequired

        Machine-readable code. Branch on this, never on message.

      • messagestringrequired
      • request_idstringrequired
      • detailsobject

        For validation_failed, the messages per parameter.

  • 403The key is right but cannot do this: insufficient_scope (the key lacks the scope of the call), connection_paused or connection_not_active (the connection is paused or not turned on yet).
    Headers
    • X-Request-Id The id of this call. Quote it if you contact support; errors repeat it as request_id.
    • errorobjectrequired
      Child attributes
      • codestringrequired

        Machine-readable code. Branch on this, never on message.

      • messagestringrequired
      • request_idstringrequired
      • detailsobject

        For validation_failed, the messages per parameter.

  • 429rate_limited: wait for the seconds in Retry-After.
    Headers
    • X-Request-Id The id of this call. Quote it if you contact support; errors repeat it as request_id.
    • Retry-After Seconds to wait before the next call.
    • errorobjectrequired
      Child attributes
      • codestringrequired

        Machine-readable code. Branch on this, never on message.

      • messagestringrequired
      • request_idstringrequired
      • detailsobject

        For validation_failed, the messages per parameter.

Request
curl -X GET https://api-commerce.nucleoplatform.com/api/commerce/v1/ping \
  -H "Authorization: Bearer $NUCLEO_ACCESS_TOKEN" \
  -H 'Accept: application/json'
Response
{
  "api_version": "v1",
  "company": {
    "id": 1042,
    "name": "Acme Apparel"
  },
  "connection": {
    "id": "6a1f2c3d-4e5b-4c6d-8e7f-9a0b1c2d3e4f",
    "name": "Acme ERP",
    "status": "active"
  },
  "scopes": [
    "orders:read",
    "returns:read",
    "inventory:read",
    "locations:read"
  ],
  "webhooks": {
    "enabled": true,
    "events": [
      "order.created",
      "order.status_changed",
      "shipment.shipped",
      "return.created",
      "return.status_changed"
    ]
  },
  "server_time": "2026-10-13T08:30:00Z"
}
Was this page helpful?