# Integration

### Components diagram <a href="#components-diagram" id="components-diagram"></a>

<figure><img src="https://2323683558-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8SVK0eP2IwFbT1kSzOyQ%2Fuploads%2FqN1hIxfQMbYf5msQhuLg%2FMobile%203.0.jpg?alt=media&#x26;token=94006fd6-ba3a-458b-a650-f9d9055b1489" alt=""><figcaption></figcaption></figure>

### General information <a href="#general-information" id="general-information"></a>

The integration endpoint is: `https://integration.enable3.io`

If no response specified in documentation means there is no response body, just status code.

### Authorization <a href="#authorization" id="authorization"></a>

All requests should have `X-API-KEY` header. The API KEY could be found in the Enable3 Admin panel.

### Limitations <a href="#limitations" id="limitations"></a>

The server IP addresses, from which requests will be called, should be whitelisted in the Enable3 Admin panel.

### **Flow**

User could be created in Enable3 side in two ways: during open the Widget or during receiving first event from the Application side.

Even if the user has never opened the widget, but the Application sent events - user will be create on Enable3 side and will start to receive rewards.