Objects

Retrieve, update, and delete Limio objects by type — subscriptions, customers, orders, identities, addresses, schedules, payment methods, subscription offers, entitlements, events, and process events. Supports pagination and relationship traversal.

Get Object

get

These APIs allow you to retrieve specific objects in Limio. You can get a subscription, customer, order, identity, address, schedule, payment method, subscription offer, user entitlement, event or process event object. You can also get a list of objects of a specific type using the Get Objects API.

Authorizations
AuthorizationstringRequired

OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.

Obtain a token via the OAuth flow described in OAuth Bearer Token.

Pass the token in the Authorization header: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequired

The type of object to operate on. Determines the shape of the response data and which fields are available.

Example: subscriptionsPossible values:
idstringRequired

The unique identifier of the object. Format varies by object type (e.g. sub-... for subscriptions, cus-... for customers, order-... for orders).

Example: sub-abcxyz123456
Responses
chevron-right
200

OK

application/json
or
or
or
or
or
or
or
or
or
get
/objects/{service}/{path_type}/{id}

Update Object

put

This API allows you to update objects in Limio. You can update a subscription, customer, order, identity, address, schedule, payment method, subscription offer, promo code, or user entitlement. It is designed to be flexible and allow you to update any field in the object.

Authorizations
AuthorizationstringRequired

OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.

Obtain a token via the OAuth flow described in OAuth Bearer Token.

Pass the token in the Authorization header: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequired

The type of object to operate on. Determines the shape of the response data and which fields are available.

Example: subscriptionsPossible values:
idstringRequired

The unique identifier of the object. Format varies by object type (e.g. sub-... for subscriptions, cus-... for customers, order-... for orders).

Example: sub-abcxyz123456
Body
namestringOptional

The object name such as the subscription name, or gift code name. Not included values will not be updated and nested values will require the structure to update. Updates will only occur for the id provided. WARNING! Changing this field might break integrations

Example: abc123
dataone ofRequired
or
or
Responses
chevron-right
200

OK

application/json
idstringOptional

The ID of the object

Example: sub-123123123
sort_keystringOptional

The sort key of the object

Example: object/subscription
dataobjectOptional

The data of the object sent in the request

Example: {"quantity":2}
put
/objects/{service}/{path_type}/{id}

Delete Object

delete

This API allows you to delete objects in Limio. Currently, only promo codes v2 are deleted via this API.

Authorizations
AuthorizationstringRequired

OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.

Obtain a token via the OAuth flow described in OAuth Bearer Token.

Pass the token in the Authorization header: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequired

The type of object to operate on. Determines the shape of the response data and which fields are available.

Example: subscriptionsPossible values:
idstringRequired

The unique identifier of the object. Format varies by object type (e.g. sub-... for subscriptions, cus-... for customers, order-... for orders).

Example: sub-abcxyz123456
Responses
chevron-right
200

OK

application/json
httpStatusCodeintegerOptional

The HTTP status code of the response

Example: 200
requestIdstringOptional

The request ID

Example: 1234ABC
attemptsintegerOptional

The number of attempts made

Example: 1
totalRetryDelayintegerOptional

The total retry delay in milliseconds

Example: 0
delete
/objects/{service}/{path_type}/{id}

Get Objects

get

These APIs allow you to retrieve a list of objects of a specific type in Limio. You can get a subscription, customer, order, identity, address, schedule, payment method, subscription offer, user entitlement, event or process event objects. Each object is returned with a summary of its data. To fetch all of the object data, use the retrieved object ID with the Get Object API.

Authorizations
AuthorizationstringRequired

OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.

Obtain a token via the OAuth flow described in OAuth Bearer Token.

Pass the token in the Authorization header: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequired

The type of object to operate on. Determines the shape of the response data and which fields are available.

Example: subscriptionsPossible values:
Query parameters
limitintegerOptional

Maximum number of objects to return. Defaults to 50 if not specified.

Default: 50Example: 10
queryMorestringOptional

Retrieves the next page of results. Use the queryMore returned in the previous response.

Example: DnF1ZXJ5VGhlbkZldGNoBQAAAAAAGH
Responses
chevron-right
200

OK

application/json
or
or
or
or
or
or
or
or
or
or
or
get
/objects/{service}/{path_type}
get

Retrieve all objects related to a specific object, identified by service, type, and ID. For example, fetch all related orders, payment methods, or schedules for a given subscription. Returns related objects across all record types. To filter by a specific record type, use the Get Object Relationships By Record Type endpoint instead.

chevron-right
lockRequired scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.

Obtain a token via the OAuth flow described in OAuth Bearer Token.

Pass the token in the Authorization header: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequired

The type of object to operate on. Determines the shape of the response data and which fields are available.

Example: subscriptionsPossible values:
idstringRequired

The unique identifier of the object. Format varies by object type (e.g. sub-... for subscriptions, cus-... for customers, order-... for orders).

Example: sub-abcxyz123456
Responses
chevron-right
200

OK

application/json

Related Objects

get
/objects/{service}/{path_type}/{id}/related
get

This API allows you to get objects related to a specific object of provided path type from a provided service using the object's ID. You can get related objects of a subscription, customer, order, identity, address, schedule, payment method, subscription offer, or user entitlement.

chevron-right
lockRequired scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.

Obtain a token via the OAuth flow described in OAuth Bearer Token.

Pass the token in the Authorization header: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
idstringRequired

The unique identifier of the object. Format varies by object type (e.g. sub-... for subscriptions, cus-... for customers, order-... for orders).

Example: sub-abcxyz123456
path_typestring · enumRequired

The type of object to operate on. Determines the shape of the response data and which fields are available.

Example: subscriptionsPossible values:
record_typestring · enumRequired

The record type of the object

Possible values:
Responses
chevron-right
200

OK

application/json

Related Objects

get
/objects/{service}/{path_type}/{id}/related/{record_type}

Add Object Relationship

post

This API allows you to add a related identity object to a specific object of provided path type from a provided service using the object's ID. You can add related objects of a subscription, customer, order, identity, address, schedule, payment method, subscription offer, or user entitlement.

chevron-right
lockRequired scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.

Obtain a token via the OAuth flow described in OAuth Bearer Token.

Pass the token in the Authorization header: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
idstringRequired

The unique identifier of the object. Format varies by object type (e.g. sub-... for subscriptions, cus-... for customers, order-... for orders).

Example: sub-abcxyz123456
path_typestring · enumRequired

The type of object to operate on. Determines the shape of the response data and which fields are available.

Example: subscriptionsPossible values:
record_typestringRequired

Only identity is allowed

Default: identity
Body

Related Object Request

idstringOptional

The identity to which you want to link the object to

Example: identity-bcc1997b17b7824caf86b06451904fb8
servicestring · enumOptional

The service of the identity

Example: limioPossible values:
Responses
chevron-right
200

OK

application/json
nullOptional
post
/objects/{service}/{path_type}/{id}/related/{record_type}

No content

Get Child Objects

get

Retrieve all child objects of a parent object, identified by service, type, and ID. Returns children across all record types. Each child object includes a summary of its data — use the Get Object endpoint with the child's ID to fetch full details.

chevron-right
lockRequired scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.

Obtain a token via the OAuth flow described in OAuth Bearer Token.

Pass the token in the Authorization header: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequired

The type of object to operate on. Determines the shape of the response data and which fields are available.

Example: subscriptionsPossible values:
idstringRequired

The unique identifier of the object. Format varies by object type (e.g. sub-... for subscriptions, cus-... for customers, order-... for orders).

Example: sub-abcxyz123456
Responses
chevron-right
200

OK

application/json

Children Objects

get
/objects/{service}/{path_type}/{id}/objects

Get Child Objects by Record Type

get

Retrieve child objects of a specific record type from a parent object. Similar to Get Child Objects, but filtered to only return children matching the specified subtype (e.g. only order children of a subscription). Each child object includes a summary of its data.

chevron-right
lockRequired scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.

Obtain a token via the OAuth flow described in OAuth Bearer Token.

Pass the token in the Authorization header: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequired

The type of object to operate on. Determines the shape of the response data and which fields are available.

Example: subscriptionsPossible values:
idstringRequired

The unique identifier of the object. Format varies by object type (e.g. sub-... for subscriptions, cus-... for customers, order-... for orders).

Example: sub-abcxyz123456
subtypestring · enumRequired

The record type of the child objects to retrieve.

Example: orderPossible values:
Responses
chevron-right
200

OK

application/json

Children Objects

get
/objects/{service}/{path_type}/{id}/objects/{subtype}

Get Object Events

get

Retrieve the event history for a specific object. Events represent actions that have been performed on or related to the object, such as creation, updates, offer changes, or cancellations. Commonly used to build an audit trail or activity log for subscriptions.

chevron-right
lockRequired scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

OAuth 2.0 Bearer token for authenticated API access. Required for order submission, object management, and administrative operations.

Obtain a token via the OAuth flow described in OAuth Bearer Token.

Pass the token in the Authorization header: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequired

The type of object to operate on. Determines the shape of the response data and which fields are available.

Example: subscriptionsPossible values:
idstringRequired

The unique identifier of the object. Format varies by object type (e.g. sub-... for subscriptions, cus-... for customers, order-... for orders).

Example: sub-abcxyz123456
Responses
chevron-right
200

OK

application/json
get
/objects/{service}/{path_type}/{id}/events

Last updated

Was this helpful?