API implementation

A clear backend contract for teams that want to ship.

The developer surface focuses on server-to-server usage, auth, contact capture, subscribers, events and platform health without exposing private credentials in the browser.

Route handlersRequest IDsRate-limit statesCloudflare-ready

Client-to-site flow

await fetch('/api/contact', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({ name, email, message })
});

Live integration

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.

Configure environment

Set ONEHUB_API_URL and ONEHUB_SITE in local, preview and production environments.

Use local site routes

Call the website API layer for auth, contact and subscriber flows so the server attaches context headers.

Inspect responses

Preserve request IDs, rate-limit headers and validation messages for support diagnostics.

Move to Workers

OpenNext builds the Next.js app into a Cloudflare Worker with web-standard fetch code.

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.

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.

await fetch('/api/contact', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({ name, email, message })
});

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.

Contact sales