Subscription Records Export
This endpoint enables you to retrieve all subscriptions data managed by Zotlo. It enables you to view active, inactive, or canceled subscriptions on the platform using various filters such as date range, package, and country. The endpoint allows you to fetch large volumes of subscription data efficiently and manage your reporting and operational workflows smoothly.
The service operates with the GET method.
Request Parameters
limit
Optional
Number of records to return in a single page. Default: 25. Maximum: 100.
country
Optional
Filters subscriptions by user country (2-letter ISO code, e.g. UK, US).
package_id
Optional
Filters subscriptions by the associated packageId.
start_date
Optional
Lists subscriptions created on or after this date. Format: YYYY-MM-DD
end_date
Optional
Lists subscriptions created on or before this date. Format: YYYY-MM-DD.
before
Optional
Cursor token to fetch the previous page. Use the value returned under paging.cursors.previous from the last response.
after
Optional
Cursor token to fetch the next page. Use the value returned under paging.cursors.next from the last response.
Sample Request
GET https://api.zotlo.com/v1/reports/activity/subscription?limit=50?&start_date=2025-11-01&end_date=2025-11-30 HTTP/1.1
AccessKey: ••••••
AccessSecret: ••••••
Content-Type: application/json
ApplicationId: •
Language: ••Successful Response
Key Response Fields
meta.requestId
Unique ID generated by Zotlo for this request (useful for debugging and support).
meta.httpStatus
HTTP status code for the response (e.g. 200).
result.data
Array of subscription records returned for this page.
result.paging.cursors.previous
Cursor token to fetch the previous page. Send this value as before in the next request.
result.paging.cursors.next
Cursor token to fetch the next page. Send this value as after in the next request.
result.paging.previous
Full URL for the previous page request (helper link).
result.paging.next
Full URL for the next page request (helper link).
Failed Response
All failed responses follow the same standard error format. (See: Error Handling)
Last updated

