# Retrieve customer timeline messages Retrieves customer timeline messages. Endpoint: GET /customers/{id}/timeline Version: latest Security: SecretApiKey, JWT ## Path parameters: - `id` (string, required) ID of the resource. ## Query parameters: - `limit` (integer) Limits the number of collection items to be returned. - `offset` (integer) Specifies the starting point within the collection of items to be returned. - `filter` (string) Filters the collection items. This field requires a special format. Use for multiple allowed values. Use for multiple fields. For more information, see Using filter with collections. - `sort` (array) Sorts and orders the collection of items. To sort in descending order, prefix with . Multiple fields can be sorted by separating each with . - `q` (string) Use this field to perform a partial search of text fields. ## Response 200 fields (application/json): - `id` (string) ID of the customer timeline custom event. Example: "tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC" - `type` (string) Type of timeline message. Enum: "account-password-reset-requested", "account-verification-requested", "aml-list-was-possibly-matched", "deposit-request-completed", "deposit-request-created", "deposit-request-expired", "deposit-request-started", "coupon-applied", "coupon-redeemed", "coupon-redemption-canceled", "custom-event", "custom-event-processed", "custom-fields-changed", "customer-bank-account-blocked", "customer-blocked", "customer-comment-created", "customer-created", "customer-merged", "customer-payment-card-blocked", "customer-requested-otp", "customer-tagged", "customer-untagged", "default-payment-instrument-changed", "email-message-sent", "experian-check-performed", "invoice-abandoned", "invoice-created", "invoice-disputed", "invoice-issued", "invoice-paid", "invoice-partially-paid", "invoice-partially-refunded", "invoice-past-due", "invoice-refunded", "invoice-reissued", "invoice-revenue-recognized", "invoice-voided", "kyc-document-accepted", "kyc-document-created", "kyc-document-modified", "kyc-document-rejected", "kyc-document-reviewed", "kyc-request-fulfilled", "lead-source-changed", "order-activated", "order-canceled", "order-churned", "order-completed", "order-created", "order-downgraded", "order-paid-early", "order-reactivated", "order-renewed", "order-trial-ended", "order-upgraded", "payment-card-expiration-was-modified", "payment-card-expired", "payment-instrument-created", "payment-instrument-deactivated", "primary-address-changed", "quickbooks-customer-created", "quickbooks-customer-task-failed", "quote-canceled", "quote-created", "quote-expired", "quote-issued", "quote-order-attached", "quote-recalled", "quote-rejected", "quote-updated", "refund-was-reflected-in-invoices", "subscription-paused", "subscription-resumed", "subscription-trial-end-changed", "transaction-abandoned", "transaction-amount-discrepancy-found", "transaction-approved", "transaction-canceled", "transaction-declined", "transaction-discrepancy-found", "transaction-disputed", "transaction-reconciled", "transaction-refunded", "transaction-voided", "transaction-waiting-gateway" - `customEventType` (string,null) Timeline custom event type. Used with type. This value must be defined using the [Create customer timeline custom event type](https://www.rebilly.com/catalog/all/customers-timeline/postcustomertimelinecustomeventtype) operation. - `triggeredBy` (string) Specifies who, or what, triggered the timeline event. Enum: "rebilly", "app", "direct-api" - `message` (string) Detailed message description. - `extraData` (object) Additional data. - `extraData.actions` (array) Actions available for a timeline message. If no actions are available, this field is empty. - `extraData.tables` (array) Table data that is attached to the timeline message. - `extraData.tables.type` (string) Enum: "list", "one-columns", "two-columns", "three-columns" - `extraData.tables.title` (string) Data table title. - `extraData.tables.footer` (string) Data table footer. - `extraData.author` (object) Author of the timeline message. - `extraData.author.userFullName` (string) Author's full name. - `extraData.author.userId` (string) Author's user ID. Example: "usr_0YVCEENYJ3D7Q9EN6BN16HA0G4" - `extraData.mentions` (object) User mentions, or tags, in a timeline. Example: {"@test@mail.com":"userId-1"} - `extraData.links` (array) Links that are attached to a timeline message. - `extraData.links.resourceType` (string) Enum: "kyc-document", "invoice", "subscription", "transaction", "email-message", "dispute", "coupon", "external" - `extraData.links.resourceId` (string) Unique resource ID. - `extraData.links.placeholder` (string) Example: "KYC document" - `extraData.links.externalUrl` (string) Example: "http://example.com" - `occurredTime` (string) Date and time when the timeline message occurred. - `_links` (array) Related links. - `_links.href` (string) Link URL. - `_links.rel` (string) Type of link. Enum: "self" ## Response 401 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 403 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.