1. Overview

• Definition: The API Connector receives real-time data over a webhook/API. Instead of Mobio pulling from your source, your system pushes (POST) data directly to a shared Mobio endpoint.
• Value: Keeps your campaigns running on fresh data — this is the single entry point for every request before being processed.
• Users: Data Engineer, Backend Developer (partner systems).

2. Terminology & Configuration Parameters

• Request Method — The default communication method for this endpoint is POST.
• Request Header (Authentication Header) — A key-value pair that identifies and authorizes each request.
• Body Payload — The data packaging format. Mobio defaults to JSON and has a bulk limit of 200 records per request.

3. Prerequisites

• Related article: Overview of Data Flow Operation – Data Source
• Create an Application first: You need an Application already set up in Mobio to handle authentication (generate the AppKey) before configuring the API Connector. See Manage Applications.
• Permissions: Your Mobio account must have the INTEGRATION RBAC permission. See the RBAC permissions guide.
• Access Path: Go to Settings → Data Integration → Connector → Data Source → Create New Data Source, or Settings → Data Integration → Data Flow → Data Source → Add New.

4. Step-by-step instructions

Step 1: Create the API Connector

• Go to the Data Source management screen.
• Select Add New Data Source → HTTP API.

Step 2: Enter identification details

• Source name: Enter a unique name (up to 200 characters) — it can’t duplicate another source name in your Tenant.
• Source description: Describe the data flow (up to 500 characters).

Step 3: Enter authentication details (Credentials)

• Request URL: Mobio pre-fills the API endpoint. Click Copy to share it with your dev team.
• Application: Select the authenticated application from the dropdown list.
• Method: Defaults to POST (can’t be edited).
• Request Header: Once you select an Application, Mobio auto-fills 4 read-only security headers: X-Merchant-ID, Mobio-Connector-Identifier, Mobio-Access-Token, Mobio-Connector-AppKey.
• Click + Add New to send additional custom key-value pairs (up to 50 pairs).
• Query Parameter: An auto-generated string carrying the Application’s security parameters (e.g., ?x-merchant-id=...). Can’t be edited.
• Request Body: Defaults to application/json (can’t be edited).

Step 4: Save the connection

• Unlike Database Connectors, an API Connector always returns a 200 OK response — so there’s no “test connection” step here.
• Click Save. The connection status switches to ON.

5. Operational Rules

• Bulk request limit: Each request batch can include up to 200 records.
• Email alerts: Off by default. Turn this on and enter an email address to receive 3 sync reports a day (9 AM, 2 PM, 6 PM, Mobio server time). Disconnection alerts are sent immediately.

6. Frequently Asked Questions (FAQ)

• Q: Can I assign the same Application to multiple Connectors
  • A: Yes. You can reuse a single Application’s AppKey across multiple data sources or destinations to simplify management.

7. Next Steps

API Connector Report