Data moves through files and manual tasks
Contacts, order states, and attributes arrive late across systems.
REST API y Gobernanza Empresarial
Diseñado para desarrolladores, estructurado para agencias.
Automatiza cualquier flujo de email con endpoints REST limpios, recibe Webhooks en tiempo real y gestiona de 1 a 25 subusuarios aislados en una sola cuenta.
REST API y Webhooks ultrarrápidos1–25 subusuarios con espacios aisladosPortal de clientes en marca blanca
REST API · webhook · role
POST /api/v1/subscribers
Authorization: Bearer ••••••••
{
"workspace": "client-a",
"role": "campaign_manager",
"event": "subscriber.created"
}Cuellos de botella operativos
Gestionar varias marcas en una sola cuenta genera riesgos de seguridad.
Las agencias y grupos empresariales necesitan entornos completamente separados, permisos granulares y credenciales API independientes para garantizar la privacidad.
Source systems never receive delivery outcomes
Bounce, click, and subscriber status do not return to the CRM.
Every team member shares one account
The business cannot determine who viewed, changed, or launched a campaign.
Several clients share one data space
Agencies struggle to separate workspaces, assets, and permissions by client.
Cuatro capacidades clave
Four layers to separate when designing the operating model.
API integration, webhooks, subusers, and roles work together, but none replaces another.
REST API
Read and write data with controlled access
Connect supported contacts, lists, campaigns, and resources to the source system.
WEBHOOK
Push events back to receiving systems
Send the state required for a CRM or application to continue its workflow.
SUBUSER
Create a separate identity for each person
Avoid shared passwords and assign each user to the appropriate workspace.
ROLE & ACCESS
Scope permissions to responsibility
Separate viewing, creation, approval, sending, and sensitive configuration access.
Comparativa operativa
Move from “we have an API” to an integration that can be operated long term.
Decision makers need visibility into data flow, access rights, and traceability together.
Criterio de decisiónEnfoque anteriorCon eMailBase
Bring data in
Use CSV files and repeated scheduled tasks.
Sync data through the REST API as part of the workflow.
Receive events
Check reports manually.
Send status back to the source system by webhook.
Team accounts
Share login credentials.
Give every member a separate subuser.
Approval
Anyone can change and send.
Use roles to limit actions by responsibility.
Traceability
The source of a change is unclear.
Organize access control by user and workspace.
Dentro del producto
Real API documentation with enough context for the integration team.
The API documentation shows the base URL, authentication method, and response structure. Subuser and role management remain separate to avoid confusing integration with access control.
Integration base URL
Bearer token in the request header
Returned response format
Métricas que conviene seguir
Evalúa el cambio mediante señales operativas.
Track successful requests, authentication failures, and data errors by endpoint.
Measure from event creation until the receiving system completes processing.
Review users, roles, and workspace access that are still required.
Preguntas frecuentes
Questions about integration and access control.
Define data scope, permissions, and error handling before issuing credentials.
Your system usually calls an API to read or write; eMailBase sends a webhook after an event occurs.
Not necessarily. A subuser is an identity; permissions and workspace access must follow the organization model.
Only an appropriate technical administrator. Store tokens securely, limit scope, and revoke them when no longer needed.
Design a controlled integration
Map data flows and access rights before issuing a token.
Start with one endpoint, one webhook, and one test role to validate the full lifecycle.