Data moves through files and manual tasks
Contacts, order states, and attributes arrive late across systems.
REST API & 엔터프라이즈 거버넌스
개발자를 위한 정교한 API, 에이전시를 위한 표준화.
표준 REST API로 모든 이메일 워크플로우를 자동화하고 실시간 Webhooks를 수신하며, 단일 구독으로 1~25개의 독립 클라이언트 환경을 통제하세요.
초고속 REST API & Webhooks1~25개 독립 서브 유저 격리 환경자체 브랜드 화이트라벨 포털
REST API · webhook · role
POST /api/v1/subscribers
Authorization: Bearer ••••••••
{
"workspace": "client-a",
"role": "campaign_manager",
"event": "subscriber.created"
}운영 병목 지점
하나의 계정에 다수 브랜드를 혼용 관리하는 것은 심각한 보안 위험입니다.
에이전시 및 멀티 브랜드 기업은 데이터 유출 방지와 발송 평판 보호를 위해 완벽히 격리된 환경과 전용 API 키가 필수적입니다.
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.
네 가지 핵심 역량
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.
운영 방식 비교
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.
비교 항목기존 방식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.
제품 화면
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
추적할 지표
운영 신호로 개선 효과를 평가하세요.
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.
자주 묻는 질문
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.