Unauthorized — the request lacks valid authentication credentials. Verify your Bearer token or API key is correct and has not expired.
application/json
502
Bad Gateway — an upstream service returned an unexpected response. This typically indicates an issue with the request payload (e.g. invalid field values, missing required fields) or a transient infrastructure error. Retry the request, and if the issue persists, verify the request body matches the expected schema.
application/json
get
/objects/salesforce/identities/{id}/subscriptions
Add a Timeline Event
post
Currently supported for subscriptions. To create a custom Event and attach it to that specified Object’s Timeline.
Authorizations
AuthorizationstringRequired
OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.
Pass the token in the Authorization header: Bearer <token>
Body
forSubscriptionone ofRequired
Subscription to add the event for
or
namestringRequired
Event name
Example: Order Received
typestringRequired
Domain/type of event
Example: order.event_received
sourcestringOptional
Source of the event e.g. system, user, webhook
Example: webhook
Responses
200
OK
application/json
idstringRequired
Limio event ID generated for the created event
Example: event-03bc891227308ae7c7a258240ac60b82
referencestringRequired
Limio event reference generated for the created event
Example: 3NI4H49PGHBG
statusstringRequired
Processing status of the event
Example: submitted
400
Bad request (missing or invalid fields)
401
Unauthorized — the request lacks valid authentication credentials. Verify your Bearer token or API key is correct and has not expired.
application/json
404
Not found
502
Bad Gateway — an upstream service returned an unexpected response. This typically indicates an issue with the request payload (e.g. invalid field values, missing required fields) or a transient infrastructure error. Retry the request, and if the issue persists, verify the request body matches the expected schema.
application/json
post
/timeline/subscription
Get Subscription Timeline
get
Retrieves timeline data for a given subscription or customer by ID. This API aggregates relevant events, payment methods, addresses, offers, and schedules to create a chronological activity history.
For subscriptions path parameter: Returns timeline for that specific subscription
For customers path parameter: Returns timeline for all subscriptions owned by that customer
Authorizations
AuthorizationstringRequired
OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.
Pass the token in the Authorization header: Bearer <token>
Path parameters
path_typestring · enum · max: 20Required
The type of entity to retrieve timeline for
Example: subscriptionsPossible values:
idstring · max: 60Required
The unique identifier of the subscription or customer
Example: sub-fdb5ff44f3513733c91869c43fdd37ba0
Responses
200
Successfully retrieved timeline data
application/json
400
Bad request - Invalid parameters
application/json
401
Unauthorized — the request lacks valid authentication credentials. Verify your Bearer token or API key is correct and has not expired.
application/json
404
Subscription or customer not found
application/json
502
Bad Gateway — an upstream service returned an unexpected response. This typically indicates an issue with the request payload (e.g. invalid field values, missing required fields) or a transient infrastructure error. Retry the request, and if the issue persists, verify the request body matches the expected schema.