Changelog

Changelog of news and updates for the Chattigo APIs.

2026-10-08 — API ISV: media

New Media page with the current download, upload and delete routes of the ISV API.
New Media v2 page with the correction of the media URL shape: GET /{version}/{did}/media/{media_id} and POST /{version}/{did}/media, with the channel first and the media identifier last, like the rest of the API.
The previous routes GET /{version}/{id}/{did}/media and POST /{version}/{did}/uploads keep working unchanged.
On the channel-first routes, the download reports the content type, the real size and a filename, and the upload declares the file type Meta expects.

In the Massive API, the recipient limit per send is configurable, with 1000 by default. Exceeding it returns 400 with the error code destination_limit_exceeded, and the count is taken over the list exactly as received, so repeated recipients count.
New optional allowDuplicates field (boolean, defaults to false) on the Massive API: when omitted or false, repeated recipients are removed during processing; when true, they are all sent.
New optional allow_duplicates field (boolean) on the BSP API send endpoint, with the same behavior: duplicate removal happens during processing, not in the API.

POST /v1/templates/{did} now accepts message_send_ttl_seconds to customize the template time-to-live (TTL); it is passed directly to Meta.
PUT /v1/templates/{did}/{messageTemplateId} now returns changed (boolean) in the response: true when the template was updated in Meta, false + message when there were no differences (differs()=false). Only components is required in the body.
GET /v1/templates excludes direct-message templates (isDirectMessage: true) from the regular listing.

GET /v1/templates returns one tuple per template with channel_campaigns (assigned campaigns and channels).
New fields filter with whitelist (id, waba_id, client_id, active, namespace, meta_template, channel_campaigns); total, page and pageSize are always returned.
New deleted (tri-state: true → only deleted, false/omitted → excludes) and campaign_name filters (exact match, allows fetching Unassigned templates).
Authorization hardening: tokens without BSP_CN only see their campaigns; tokens with BSP_CN must provide client_id.

New Groups API support: get group info, get group join requests, and remove group participants (with user_id or user).
New Block Users API support: block/unblock users and list blocked users.
Both under /business_identifiers/{v}/..., with required-field validation before calling Meta.

Support for Business-scoped user IDs (BSUID) and Parent BSUID in messaging and webhooks.
Send messages with recipient (BSUID/Parent BSUID) on /messages and /marketing_messages.
Business Username and Contact Book endpoints under /business_identifiers/{v}/....
New 2026 webhook fields: user_id, parent_user_id, username, from_user_id, from_parent_user_id.

New GET /v1/pricing endpoint: per-message rate by market and category, following the official rate cards. Includes GET /v1/pricing/markets.
Support for AUTHENTICATION (OTP) templates with OTP buttons (COPY_CODE, ONE_TAP, ZERO_TAP), add_security_recommendation and code_expiration_minutes.
Security hardening: JWT validation, media URL restrictions, and TLS protection.

Media download with configurable size cap and streamed response.
Channel-campaigns restructured under /v1/templates/{messageTemplateId}/channel-campaigns (no DID in the route).
Full template persistence with its identifier, status and Meta namespace.

See the BSP API reference for endpoint details.