Omni Link
Get subscribers
Returns a list of subscribers, could paginated using the page and limit query parameter
Authorization
bearerAuth AuthorizationBearer <token>
JWT access token returned by Signing In (POST /auth/v1/tokens/).
In: header
Query Parameters
page?number
limit?number
Range
value <= 100Default
10Response Body
application/json
curl -X GET "https://example.com/v1/subscribers"{ "page": 0, "hasMore": true, "pageSize": 0, "data": [ { "_id": "string", "firstName": "string", "lastName": "string", "email": "string", "phone": "string", "whatsappNumber": "string", "locale": "string", "subscriberId": "string", "isOnline": true, "lastOnlineAt": "string", "_organizationId": "string", "_environmentId": "string", "deleted": true, "createdAt": "string", "updatedAt": "string", "__v": 0 } ]}Cancel triggered event DELETE
Using a previously generated transactionId during the event trigger, will cancel any active or pending workflows. This is useful to cancel active digests, delays etc...
Create subscriber POST
Creates a subscriber entity, in the Omni-Link platform. The subscriber will be later used to receive notifications, and access notification feeds. Communication credentials such as email, phone number, and whatsapp number, could be later associated to this entity.