- Getting Message Statuses
Send SMS to the list of clients
Send SMS campaigns to customers matching the filters
Send Email newsletter according to the list of clients
Send email campaigns for clients matching the filters
Get notification settings in a location
Get User Notification Settings
Change User Push Notification Settings
Getting Message Statuses
| Number | Title |
|---|---|
| 1 | Delivered |
| 2 | Not delivered |
| 4 | Sent to phone |
| 8 | Transferred to the operator |
| 16 | Rejected by operator |
| 52 | Not enough funds |
In the event of an error, the corresponding HTTP status code is returned. In some cases, a descriptive error message is also included in the response. The following error codes may be returned by all API methods:
| error code | Http status code | Title | Description |
|---|---|---|---|
| 5 | 400 | ENTITY_VALIDATION_ERROR | The request body did not pass validation |
| 10 | 400 | FIELD_VALIDATION_ERROR | Parameter not validated |
| 15 | 403 | ACCESS_FORBIDDEN | The action is not available, the application does not have the required permissions. |
| 20 | 401 | INVALID_PARTNER_TOKEN | partner_token missing or invalid |
| 30 | 404 | RESOURCE_NOT_FOUND | The resource at the requested path does not exist |
When sending SMS, the delivery_callback_url attribute is passed in the request - this is the url to which message statuses should be sent.
Use it to send message statuses. Url to which message statuses should be sent - https://app.alteg.io/smsprovider/status/callback/{partner_token}
Security
BearerPartnerUser
- Mock serverhttps://developer.alteg.io/_mock/en/b2b-v1/openapi/delivery/status
- Productionhttps://api.alteg.io/api/v1/delivery/status
curl -i -X POST \
https://developer.alteg.io/_mock/en/b2b-v1/openapi/delivery/status \
-H 'Accept: application/vnd.api.v2+json' \
-H 'Authorization: Bearer <YOUR_Bearer {PartnerToken}, User {UserToken}_HERE>' \
-H 'Content-Type: application/json' \
-d '[
{
"id": "232674",
"status": 1,
"payment_sum": 0.045,
"currency_iso": "EUR",
"parts_amount": 2
}
]'