Migrating from v1

v1 has been removed

API v1 is no longer served. Requests to /api/v1/* will not succeed, and there is no v1 reference page. If an integration still points at it, it is already failing — move it to v2.

This page replaces the old v1 guide, which documented endpoints that no longer exist.

What to change

1. The base URL

- https://orqestra.id/api/v1
+ https://orqestra.id/api/v2

Your existing wa_pk_ token keeps working. Tokens are not versioned, so there is nothing to reissue.

2. Message sending consolidated

v1 had separate endpoints per message kind. v2 has one endpoint with a type discriminator.

- POST /messages/text      { "waId": "...", "text": "..." }
- POST /messages/template  { "waId": "...", "templateName": "..." }
+ POST /messages           { "to": "...", "type": "text", "text": "..." }
+ POST /messages           { "to": "...", "type": "template", "template": { ... } }

Note the field rename: waId became to, because the same endpoint now addresses Instagram as well as WhatsApp.

3. Channel targeting

Endpoints that touch a channel accept an optional channelId. An organization with two WhatsApp numbers can now say which one to send from. Omit it and Orqestra infers the channel from the existing chat, falling back to the organization default — which is the v1 behaviour.

New in v2

These have no v1 equivalent: segments, custom contact fields, channels, organization metadata, escalation and de-escalation, and contact import jobs.

Checklist

• Swap the base URL to /api/v2.
• Replace /messages/text and /messages/template with POST /messages.
• Rename waId to to in send payloads.
• Confirm your token carries the permissions the v2 routes require — see Authentication.
• Re-test against the playground before switching production traffic.