Object API

Access and manage key subscription commerce objects through a unified REST API.

This API enables you to retrieve and manage the following objects:

  • orders

  • customers

  • subscriptions

  • identities

  • address

  • schedules

  • payment_methods

  • subscription_offers

  • user_entitlements

  • gift_code

  • promo_codes_v2

Full documentation on how to use our Objects REST API can be found here.

Sample API methods are available below:

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

To create a Bearer token, see How to get an OAuth Bearer Token?.

Usage format: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequiredPossible values:
idstringRequiredExample: sub-abcxyz123456
Responses
200

OK

application/json
Responseone of
or
or
or
or
or
or
or
or
or
get
/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

To create a Bearer token, see How to get an OAuth Bearer Token?.

Usage format: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequiredPossible values:
Query parameters
limitnumberOptional

The number of objects to return.

Example: 10
queryMorestringOptional

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

Example: DnF1ZXJ5VGhlbkZldGNoBQAAAAAAGH
Responses
200

OK

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

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

To create a Bearer token, see How to get an OAuth Bearer Token?.

Usage format: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequiredPossible values:
idstringRequiredExample: 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
200

OK

application/json
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

To create a Bearer token, see How to get an OAuth Bearer Token?.

Usage format: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequiredPossible values:
idstringRequiredExample: sub-abcxyz123456
Responses
200

OK

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

This API allows you to get objects related to a specific object in Limio. You can get related objects of a subscription, customer, order, identity, address, schedule, payment method, subscription offer, or user entitlement.

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

To create a Bearer token, see How to get an OAuth Bearer Token?.

Usage format: Bearer <token>

Path parameters
servicestring · enumRequired

The service the object belongs to

Default: limioPossible values:
path_typestring · enumRequiredPossible values:
idstringRequiredExample: sub-abcxyz123456
Responses
200

OK

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

Last updated

Was this helpful?