Below is the description of API for adding and updating the customer profile's data in the Epsilon CDP. Requests are sent to CDP Middleware developed and maintained internally by RB.
Prerequisites
OAuth 2.0
API is secured by OAuth 2.0 authorization system, thus every call needs to have a token set.
Obtain the token set using NUTRINTG Security Integration Quick Start.
Metadata
So-called "metadata" should be available in the Epsilon CDP, so that adding data is successful. Also, it should be provided in the content of requests.
If you don't possess it yet, send an email request to CDP Middleware Team (Business Analyst and Project Manager) to add metadata - with at least 3 full business days in advance.
The email request should contain:
- Website domain
- Country
- Language
- Brand related to the website
- Platform name (e.g. Husky, Shopify)
Common HTTP Headers
Parameter name | Mandatory | Parameter description |
|---|---|---|
| Authorization | Yes | Authorization Token ( from Prerequisites ) |
Accept-language | Yes | lang ISO code - "en-US" |
Brand-org-code | Yes | → Metadata |
Client-Id | No, but should be provided if available, since it is required for the Update profile method. | Id of the customer, if available in the source system. |
Program-code | Yes | → Metadata (same value as in the "Brand-org-code" field) |
Account-source | Yes | → Metadata |
| Sourcecode | Yes | → Metadata |
Content-Type | Yes | example: application/json |
X-Source-Domain | No | example: Required if the profile should be completed with available UTM attributes from Google Analytics |
Methods:
| method | documentation | URL | Method |
|---|---|---|---|
| add Profile | NUTRTINTG Profile API - add Profile | https://api.cdp-rb.com/v2/profile | POST |
| edit Profile | NUTRTINTG Profile API - edit Profile | https://api.cdp-rb.com/v2/profile | PUT |
:
:
0 Comments