Migrate from v1
API v1 is retired. Every /v1 route now returns 410 Gone; legacy keys cannot authenticate to the current API.
Migration checklist
- Create a new
pw_v2_key in the dashboard and choose the smallest required scope preset. - Change the base URL to
/v2. - Read successful payloads from
dataand pagination frommeta.next_cursor. - Add
Idempotency-Keyto creations and actions. - Replace toggle calls with explicit
startorstopoperations. - Enable remote control locally with
pwrp remote enable, or in the desktop app under Settings > Remote Control. - Track asynchronous work through
/operationsor webhooks.
Behavior changes
API keys are managed in the dashboard. Remote actions require a current Portwarp client with remote control enabled locally.