PASAR API

🇧🇷 Zenvia ~ SMS, WhatsApp & multichannel messaging

← directory

Brazilian CPaaS leader offering one API across SMS, WhatsApp Business, email, RCS and voice channels; requests authenticate with an X-API-TOKEN header and a sandbox is provided.

View docs ↗ More Communications APIs

Get started

# Zenvia ~ SMS, WhatsApp & multichannel messaging needs an access token ~ get yours at:
# https://zenvia.github.io/zenvia-openapi-spec/v1/
curl 'https://api.zenvia.com/v2/' \
  -H 'Authorization: Bearer YOUR_TOKEN'

AI prompt

I'm integrating a Brazil API into my app.

API: Zenvia ~ SMS, WhatsApp & multichannel messaging
Provider: Zenvia
Auth: requires an access token (sign up: https://zenvia.github.io/zenvia-openapi-spec/v1/)
Pricing: paid
Base URL: https://api.zenvia.com/v2/
Important note: Brazilian CPaaS leader offering one API across SMS, WhatsApp Business, email, RCS and voice channels; requests authenticate with an X-API-TOKEN header and a sandbox is provided.

Source: Zenvia (https://zenvia.github.io/zenvia-openapi-spec/v1/)
Source type: Provider API or developer docs
Endpoint type: Provider API base URL
Integration difficulty: Needs token
Last checked: 2026-07-05
Production caveat: Keep credentials server-side and confirm current limits, pricing, and webhook/error behaviour in the provider docs.

Help me set up the correct onboarding/authentication path and make the first valid request ~ explain exactly where credentials go and what must happen before production.

Related Communications APIs