Sales and technical onboarding

Tell Essia what you need to deliver in Brazil.

Share your target users, monthly volume, OTP requirements, notification use cases and integration timeline. The form submits directly to the OneHub contact endpoint.

SalesAPI integrationOTP flowsBrazil delivery

Sales and technical onboarding

Tell Essia what you need to deliver in Brazil.

Share your target users, monthly volume, OTP requirements, notification use cases and integration timeline. The form submits directly to the OneHub contact endpoint.

Developer path

Fast enough for a prototype, explicit enough for production.

The public site shows how Essia maps to OneHub without exposing privileged credentials. Auth, contact and subscription flows go through server route handlers.

4 flows

A2P SMS, OTP, alerts and transactional notifications

Webhook

Delivery receipts and failure reasons

LGPD

Consent, purpose and data handling awareness

BRL

Brazil commercial readiness and local buying context

FAQ

Questions a Brazil SMS API buyer will ask early.

Is this only for marketing SMS?

No. Essia focuses first on A2P transactional flows: OTP, alerts, orders, billing and customer notifications. Optional promotional consent is kept separate.

Can developers test before a sales call?

Yes. The public account flow is connected to the OpenAPI-backed auth endpoints, and the developer page shows the expected integration pattern.

Does the site expose OneHub credentials?

No. Public forms call local server routes, which then forward to OneHub and attach the site context on the server.

How does Essia approach LGPD?

The public site separates account, operational and optional marketing consent, and the security pages explain data purpose, retention and user-right handling.

The site is already wired to OneHub routes.

This panel exercises the backend contract safely through the website API layer and exposes loading, empty, degraded, unauthorized and rate-limit states.

Live integration