Emarsys OAuth

Overview

Pre-built tooling

✅ Authorization
ToolsStatus
Pre-built authorization (OAuth)✅
Credentials auto-refresh✅
Pre-built authorization UI✅
Custom authorization UI✅
End-user authorization guide✅
Expired credentials detection✅
✅ Read & write data
ToolsStatus
Pre-built integrations🚫 (time to contribute: <48h)
API unification✅
2-way sync✅
Webhooks from Tenklo on data modifications✅
Real-time webhooks from 3rd-party API🚫 (time to contribute: <48h)
Proxy requests✅
✅ Observability & data quality
ToolsStatus
HTTP request logging✅
End-to-end type safety✅
Data runtime validation✅
OpenTelemetry export✅
Slack alerts on errors✅
Integration status API✅
✅ Customization
ToolsStatus
Create or customize use-cases✅
Pre-configured pagination🚫 (time to contribute: <48h)
Pre-configured rate-limit handling✅
Per-customer configurations✅

No pre-built syncs or actions available yet.

Not seeing the integration you need? Build your own independently.

Access requirements

Pre-RequisitesStatusComment
Paid dev account❓
Paid test account❓
Partnership❓
App review❓
Security audit❓

Setup guide

No setup guide yet.

Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Contribute useful links by editing this page

API gotchas

  • Emarsys offers different APIs(Emarsys core, Loyalty V4 and SMS), currently Tenklo support Emarsys core API which offers WSSE over SSL authentication.
  • When creating a new connection in Tenklo, use a combination of the username and secret that you received during onboarding. The username follows the format account_name00X, where X is a digit.
  • The OAuth Token has a fetch rate limiting of per client_id: 2 requests per minute, 10 requests per hour or per customer_id: 10,000 requests per day. For more details OAuth Token Fetch Rate Limiting
    Contribute API gotchas by editing this page

Connect to emarsys-oauth

Guide to connect to Emarsys Core API (Ouath) using Tenklo Connect.

On this page