GET
/
api
/
external
/
v2
/
changelogs
/
customers
Get customer changes events
curl --request GET \
  --url https://app.pennylane.com/api/external/v2/changelogs/customers \
  --header 'Authorization: Bearer <token>'
{
  "items": [
    {
      "id": 123,
      "operation": "insert",
      "processed_at": "2023-11-07T05:31:56Z",
      "updated_at": "2023-11-07T05:31:56Z",
      "created_at": "2023-11-07T05:31:56Z"
    }
  ],
  "has_more": true,
  "next_cursor": "SGVsbG8sIEJhc2U2NCBlbmNvZGluZyE="
}

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Query Parameters

​
cursor
string

Cursor for pagination. Use this to fetch the next set of results. The cursor is an opaque string returned in the previous response's metadata. Leave empty for the first request.

Example:

"MjAyNS0wMS0wOVQwODoyNDozOC44MTI0NTha"

​
limit
integer

Number of items to return per request. Defaults to 20 if not specified. Must be between 1 and 1000.

Required range: 1 <= x <= 1000
​
start_date
string<date-time>

Filter the changes based on the event date. The date should follow RFC3339 format. If no date is provided, the oldest changes will be returned. Changes for the last 4 weeks are retained, thus providing a start_date older than that will result in a 422 response. Providing both start_date and cursor parameters will result in a 400 response.

Response

A list of customer changes

​
items
object[]
required
​
has_more
boolean
required

Indicates whether additional results are available beyond this set. Use this flag to determine if another request is needed.

Example:

true

​
next_cursor
string | null
required

Cursor to retrieve the next set of results. Include this value in the cursor parameter of your next request to fetch subsequent items. A null next_cursor in the response indicates no further results.

Example:

"SGVsbG8sIEJhc2U2NCBlbmNvZGluZyE="