View Delivery Basic report
Copied



https://api.ocamba.com/v1/hood/reports/delivery
Copied

https://api.ocamba.com/v1/hood/reports/delivery
Delivery Basic report enables analysis of critical parameters and essential information like Delivery Date, Delivery rate, Success rate, Error rate
Rate limits:
Burst: 10/s
Steady: 150/m
Name
Descriptionsortstring
Sorts the response by specified field(s) with the option to specify sorting order (ascending by default, add prefix "-" for descending).Examples:
GET /VERSION/hood/RESOURCE_NAME?sort=name → sorts per name, ascending
GET /VERSION/hood/RESOURCE_NAME?sort=-id → sorts per id descending
GET /VERSION/hood/RESOURCE_NAME?sort=id,-name → sorts per id ascending, then name descending
See tips for the list of sortable fields.
Example: sort=-field1,field2
pagestring
The page number indicates which set of items will be returned in the response. The format of request is "page=N,M" where 'N' (required) represents page number and 'M' (optional) is number of items per page.Examples:
N=1, M=20 → returns page 1 with 20 items
N=2, M=20 → returns page 2 with 20 items (items 21-40)
N=3 → returns page 3. The number of objects returned depends on the resource settings.
Example: page=1,10
outstring
Data format output - 'csv' (default) or 'json'.Example: out=json
resolutionstring
Data resoulution, supported values 'hour', 'day'.Example: resolution=hour
fieldsstringrequired
Fields is array of dimensions and measures. You can use dimensions to categorize, segment, and reveal the details in your data. Measures contain numeric, quantitative values that you can measure. At least one measure is required.Example: delivery_date,tag_id,task_name,delivered,error_rate
200 - OK
Name
Descriptionavg_delivery_durationfloat
MeasureThe average delivery duration of request.
Example: 0.54
clickinteger
MeasureThe total number of valid clicks.
Example: 9
container_idinteger
DimensionUnique identifier assigned by the HoodEngage app for a container resource. A container is an editable resource that centralizes settings for push notifications, analytics, crash reporting, user consent, and various lead-generation features (e.g., newsletter or SMS pop-ups). These changes are applied upon the next user session or SDK run.
Example: 126598752
container_namestring
DimensionName provided by the user on creation for a container.
Example: BBC Network US
deliveredinteger
MeasureThe total number of delivered messages.
Example: 888248
delivery_datedate
DimensionThe execution date.
Example: 2021-12-27
delivery_ratefloat
MeasureThe rate of delivered to total users.
Example: 0.54
error_ratefloat
MeasureThe rate of undelivered to success.
Example: 0.54
failedinteger
MeasureThe total number of users failed to receive message.
Example: 9
failure_ratefloat
MeasureThe rate of total failed to total users.
Example: 0.54
integration_idstring
DimensionA unique ID (e.g., "SMS") representing the specific integration or endpoint used for message delivery. For instance, a Twilio integration, custom email connector, or in-house push gateway.
Example: SMS
integration_namestring
DimensionA descriptive name (e.g., "Telesign SMS") for the integration or connector. Useful for distinguishing different implementations or accounts of the same provider type.
Example: Telesign SMS
provider_error_ratefloat
MeasureThe rate of provider failed to total users.
Example: 0.54
provider_failedinteger
MeasureThe total number of users failed to send message to.
Example: 9
provider_idstring
DimensionA unique identifier for the Provider generated by the HoodEngage platform. This ID helps track which provider responsible for delivering the messages to end-user.
Example: 1
provider_namestring
DimensionA human-readable name of the Provider. Allows quick identification of the delivery service or platform used. example: 'Telesign'
provider_typestring
DimensionThe type of provider used for message delivery (e.g., "SMS", "Email", "Push"). This classification helps distinguish different delivery channels.
Example: SMS
spam_clickinteger
MeasureThe total number of spam clicks.
Example: 9
successinteger
MeasureThe total number of users successfully sent message to.
Example: 9
success_ratefloat
MeasureThe rate of success to total users.
Example: 0.54
tag_idinteger
DimensionDEPRACATED Unique application identifier generated by HoodEngage.
Example: 126598752
tag_namestring
DimensionDEPRACATED The tag name.
Example: Demo tag
task_idinteger
DimensionDEPRACATED Unique task identifier generated by HoodEngage.
Example: 1002600
task_namestring
DimensionDEPRACATED The task name.
Example: Demo task
total_clickinteger
MeasureThe total number of all clicks.
Example: 9
total_failedinteger
MeasureThe total number of users failed to receive message and to send message to.
Example: 9
total_userinteger
MeasureThe total number of users targeted by the task or campaign. Typically determined by combining and deduplicating segments or subscriber lists. example: 888248
undeliveredinteger
MeasureThe total number of undelivered messages.
Example: 48
1 Sortable fields are: delivery_date, tag_id, tag_name, container_id, container_name, task_id, task_name, provider_type, provider_id, provider_name, integration_id, integration_name, total_user, delivered, undelivered, success, failed, provider_failed, total_failed, success_rate, delivery_rate, error_rate, provider_error_rate, failure_rate, avg_delivery_duration, click, spam_click, total_click.
2 Filterable fields are: delivery_date, tag_id, tag_name, container_id, container_name, task_id, task_name, provider_type, provider_id, provider_name, integration_id, integration_name, total_user, delivered, undelivered, success, failed, provider_failed, total_failed, success_rate, delivery_rate, error_rate, provider_error_rate, failure_rate, avg_delivery_duration, click, spam_click, total_click.
3 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.
4 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.
1 When filtering stat_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.
- 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.
- 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.
- 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.