View SMS-click report
View SMS-click report
Sortable fields are: click_date, user_id, profile_id, task_id, task_name, tag_id, tag_name, container_id, container_name, delivery_date, tag_type, container_type, integration_id, integration_name, provider_id, provider_name, destination_url, sender, recipient, spam, spam_reason.
Filterable fields are: click_date, user_id, profile_id, task_id, task_name, tag_id, tag_name, container_id, container_name, delivery_date, tag_type, container_type, integration_id, integration_name, provider_id, provider_name, destination_url, sender, recipient, spam, spam_reason.
To get data by the time in your local time zone, you should set tz query parameter to the specific time zone. See the list of valid time zones here -> https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List.
For easier search, Reports API gives you the possibility of using one of the following labels: today, yesterday, last-7-days, last-30-days, last-24-hours, this-month, last-month, current-hour, last-hour, last-48-hours, last-2-days, month-to-date, month-to-yesterday, quarter-to-date.
When filtering click_date, use one of the following formats:
- Single format: YYYY-mm-dd;
Displaying stats for this specific day - Range format: rf:YYYY-mm-dd,YYYY-mm-dd;
Requires usage of the range operators:- r - range - The value must be in a specified open range, where both endpoints are excluded.
- rf - range full - The value must be in a specified closed range, where both endpoints are included.
- rl - range left - The value must be in a specified half-open range, where only left or start point is included.
- rr - range right - The value must be in a specified half-open range, where only right or end point is included.
Displaying stats in this specific range.
- r - range - The value must be in a specified open range, where both endpoints are excluded.
- Hour range format: rl: YYYY-mm-dd hh:00:00,YYYY-mm-dd hh:00:00
If you exclude this parameter, the default setup displays “today” stats.
Rate limits:
- Burst: 10/s
- Steady: 150/m
Query parameters
parametersResponse schemas
curl -X GET \
"https://api.ocamba.com/v1/hood/reports/click/sms" \
-H "Authorization: Bearer {TOKEN}"const url = 'https://api.ocamba.com/v1/hood/reports/click/sms';
const options = {
method: 'GET',
headers: {
Authorization: `Bearer {TOKEN}`
}
};
try {
const response = await fetch(url, options);
const data = await response.json();
console.log(data);
} catch (error) {
console.error(error);
}$ch = curl_init("https://api.ocamba.com/v1/hood/reports/click/sms");
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "GET");
curl_setopt($ch, CURLOPT_HTTPHEADER, [
"Authorization: Bearer {TOKEN}"
]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);Responses
200 OK
[
{
"click_date": "2024-07-15T00:00:00Z",
"profile_id": "17210268627433927191",
"task_id": "0",
"tag_id": "15190",
"tag_name": "Tag_example",
"tag_type": "unknown",
"delivery_date": "2024-07-15T07:03:11Z",
"provider_id": "1008",
"provider_name": "provider_sms",
"integration_id": "1492",
"integration_name": "Integration_example",
"destination_url": "https://ocamba.com"
}
]
400 Bad Request
{
"code": 400,
"title": "Bad request.",
"message": "The request is not valid.",
"trace_id": "99a84211-f73d-4ff8-acdf-eb3e06bb9d62"
}
500 Internal Server Error
{
"code": 500,
"title": "Internal server error.",
"trace_id": "99a84211-f73d-4ff8-acdf-eb3e06bb9d62"
}