From Green API to Blueticks in 10 minutes.

Sign up at api.blueticks.co (3-day free trial, no card). Copy the live key from the dashboard. One key replaces every Green API instance pair you're running.

Green API encodes the method name in the URL path; Blueticks uses HTTP verbs + REST resources. sendMessage and sendFileByUrl both become POST /v1/messages. getChatHistory becomes GET /v1/chats/{chat_id}/messages. See the table above for every mapping.

Drop the URL-embedded {idInstance}/{apiTokenInstance} entirely. Add Authorization: Bearer bt_live_••• instead. One header replaces both path segments.

Blueticks accepts <digits>@c.us and <groupId>@g.us verbatim — no rewrite needed. E.164 (+14155550123) also works. Pick whichever your code already uses.

POST /v1/webhooks with { url, events[] }. The response includes a one-time HMAC secret — store it; we sign every delivery with it. Events deliver in real time from registration onward.

Green API delivers { typeWebhook, instanceData, messageData, … }. Blueticks delivers { id, type, created_at, data } with Blueticks-Webhook-{Id,Timestamp,Signature} headers. Verify the HMAC using the secret from step 5.

You are migrating my codebase from Green API (green-api.com) to Blueticks.

Reference docs (consult for exact request/response shapes):
  https://dev.blueticks.co/docs/api

# Endpoint mapping (per-method, NOT a host find-replace)

| Green API                                              | Blueticks                                |
|--------------------------------------------------------|------------------------------------------|
| POST /waInstance{id}/sendMessage/{token}               | POST /v1/messages   { to, text }         |
|   { chatId, message }                                  |                                          |
| POST /waInstance{id}/sendFileByUrl/{token}             | POST /v1/messages   { to, media_url,     |
|   { chatId, urlFile, fileName, caption }               |                       media_caption }    |
| POST /waInstance{id}/getChatHistory/{token}            | GET  /v1/chats/{chat_id}/messages        |
|   { chatId, count }                                    |   ?limit=N&cursor=…                      |
| Webhook config (SetSettings.webhookUrl)                | POST /v1/webhooks                        |
|                                                        |   { url, events[] } → returns { secret } |

# Auth
- Strip {idInstance} and {apiTokenInstance} from every URL.
- Add header: Authorization: Bearer ${BLUETICKS_API_KEY}
- One Blueticks key replaces all Green API instance pairs. To send from a
  specific connected number, add { from: "+15551234567" } in the request body.

# Chat IDs
- Keep your existing <digits>@c.us and <groupId>@g.us as-is — Blueticks
  accepts both verbatim. E.164 (+14155551234) also works. Don't rewrite.

# Webhook handler
- Green API body:  { typeWebhook, instanceData, idMessage, senderData, messageData, … }
- Blueticks body:  { id, type, created_at, data }
- Headers on every delivery: Blueticks-Webhook-Id, Blueticks-Webhook-Timestamp,
  Blueticks-Webhook-Signature (HMAC-SHA256 of "${timestamp}.${rawBody}"
  using the secret returned at registration).
- Update your event-type switch: Green API discriminates on typeWebhook
  (incomingMessageReceived, outgoingAPIMessageReceived, stateInstanceChanged, …).
  Blueticks discriminates on type (message.queued, message.sending,
  message.delivered, message.failed, message.read, session.connected,
  session.disconnected, campaign.{started,paused,resumed,completed,
  aborted}) — see /docs/webhooks for the canonical list.

# Things WITHOUT a 1:1 — flag and stop, don't paper over
- Polling: ReceiveNotification / DeleteNotification (webhooks only on Blueticks)
- Group writes: CreateGroup, AddGroupParticipant, SetGroupAdmin, UpdateGroupName
- Message types: polls, location, contact (vCard), interactive buttons, forwards
- Instance lifecycle: Reboot, Logout, QR fetch, GetStateInstance

# Closing checklist
1. Set BLUETICKS_API_KEY=bt_live_… in env / secret manager.
2. Run the test suite. Update mocks/fixtures to the new response shapes.
3. Smoke one real send: `curl -H "Authorization: Bearer $BLUETICKS_API_KEY" \
     -d '{"to":"+15551234567","text":"migration smoke"}' \
     https://api.blueticks.co/v1/messages`
4. Register the webhook last, after the handler verifies HMAC correctly.

Don't touch anything except API call sites, the webhook handler, and config.
If you hit a Green API method without an obvious mapping, surface it in your
output and STOP — those need a human decision.