Retrieve all events for a pixel
GET/pixels/:pixel_id/events
Retrieve all events for a pixel within a given date interval. The maximum interval is 60 days between the from and to dates. The events are returned in reverse chronological order.
When a response is paginated, the response headers will include a link header. The link header will be omitted if all results fit on a single page.
The link header provides the URL for the previous, next, first, and last page of results:
- The URL for the previous page is followed by rel="prev".
- The URL for the next page is followed by rel="next".
- The URL for the last page is followed by rel="last".
- The URL for the first page is followed by rel="first".
In some cases, only a subset of these links are available. For example, the link to the previous page won't be included if you are on the first page of results.
If you are paginating through the events, note that the data is not stable. If new events are added while you are paginating, you may see the same event again on the next page, so you should use the event ID to determine where to start the next page.
The client ID must have the shop_user
role.
Request
Responses
- 200
- 400
- 401
- 404
A Bad Request response indicates that the server cannot or will not process the request due to something that is perceived to be a client error
An Unauthorized response indicates that the request has not been applied because it lacks valid authentication credentials for the target resource
A Not Found response indicates that the origin server did not find a current representation for the target resource