Track on the workspace's own 17TRACK key (admin)
PUT/api/integrations/shipment-tracking/key
Doc 83 Faz C. The key is checked with 17TRACK (getquota) before it is
saved — 422 on api_key when 17TRACK refuses it, 503 when 17TRACK
cannot be reached. Saved encrypted, never returned (only its last four
characters). Switches tracking on, also where ConnectWiz's 17TRACK
account is not set up. New numbers go to this key and spend its own
17TRACK quota (not the workspace's monthly allowance, not its wallet);
numbers already registered stay on their account until they finish,
except those on a previous own key this one replaces, which stop
(tracker_error: own_key_removed). The customer must paste
account.webhook_url into its own 17TRACK dashboard.
Request
Responses
- 200
- 403
- 422
- 503
Saved.
Authenticated but not allowed.
The request failed validation.
17TRACK could not be reached; nothing was saved.