Store NuORDER Token
POST/api/nuorder/instances/:integrationInstance/token
Connects with a token pair the brand already approved (NuORDER → Admin → API Management → Approved Applications) instead of the verifier flow. The pair is validated against NuORDER (GET /api/v3.0/warehouses) BEFORE it is saved, so a rejected pair leaves the instance's connection untouched (422). The first successful connection of a portal queues the initial catalog + order import once.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body: token, token_secret (both required); optional consumer_key + consumer_secret (each required with the other) — corrected consumer credentials, validated with the pair and saved only when NuORDER accepts them.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.