# I. Testing Abenla docs with Iterable

## Abenla Docs
What Abenla gives us for using demo account

https://api.abenla.com/api/Help
UserName: ABT2G6N
LoginPassword: 5M33547UU
SendSmsPassword: 1DH34L439
ServiceTypeId=30
Brandname = ABENLA
SMS content: ABENLA - Ma truy cap cua ban la 123456 (Có thể thay thế mã OTP bằng dãy số từ 4 đến 7 ký tự)

SMS status api:
https://api.abenla.com/api/Help/ResourceModel?modelName=SmsStatus
They said that Status 1 2, 11,12, 16,17 are not final status of messages

Note that SMS message content needs to be registered before using.

# II. Testing Abenla integration with Iterable
## 1. Setup workflow webhook
Create a webhook with this endcoded url

HTTP method: Get

URL: https://api.abenla.com/api/SendSms?loginName=ABT2G6N&sign=31b23a25e7157e5094c50f22c039169b&serviceTypeId=30&phoneNumber={{phone_number}}&message=ABENLA%20-%20Ma%20truy%20cap%20cua%20ban%20la%20123456&brandName=ABENLA&callBack=false&smsGuid=1

Basically, we just add 1 data field phone_number to test the deliverablity

## 2. Setup Workflow on IT:
Under Iterable Ematic Demo setup workflow like this

1) User purchase
2) Delay 1 min
3) Send a SMS to user (must have field ```phone_number``` in the profile)
4) Delay 1 min (just to check if you flow successfully)

## 3. Create a pseudo purchase user-event
Sample payload to test on IT API docs:

- Account API key: 0017aeb528b64479ae06eadbdbfdb0da (must not be exposed!!)
- URL to API page:
https://api.iterable.com/api/docs#commerce_trackPurchase

Endpoint: POST /api/commerce/trackPurchase

{
  "user": {
    "email": "[e-mail]",
    "dataFields": {
"phone_number": "84935191807" # Ensure your have format 84xxx
     },
    "preferUserId": false,
    "mergeNestedObjects": true
  },
  "items": [
 
  ],
  "total": 0,
  "createdAt": 1617686019, # Just a timestamp event created
  "dataFields": {}
}