GET /site_migration_details

This endpoint lists the site migration details.

Servers

Request headers

Name Type Required Description
chargebee-request-origin-device String No

The device from which the customer has made the request

chargebee-business-entity-id String No

If the site has multiple business entities, you can use this custom HTTP header to specify the business entity for which Chargebee should perform the operation.

chargebee-request-origin-user String No

The email address of your customer/user. Use this when the email address has only ASCII characters.

chargebee-request-origin-ip String No

The IP address of the customer where the request originated

chargebee-request-origin-user-encoded String No

The Base64-encoded email address of your customer/user. Use this if the email address has UTF-8 characters. When this header is provided, the header chargebee-request-origin-user is ignored.

Query parameters

Name Type Required Description
limit Integer No

The number of resources to be returned.

Default value: 10

other_site_name Object No

optional, string filter
Site name to which the record is moved in/out.
Supported operators : is, is_not, starts_with

Example → other_site_name[is] = "acme-test"

entity_id Object No

optional, string filter
Id of the entity in this site.
Supported operators : is, is_not, starts_with

Example → entity_id[is] = "8axqwer7as"

entity_id_at_other_site Object No

optional, string filter
Entity Id of the record in the other site.
Supported operators : is, is_not, starts_with

Example → entity_id_at_other_site[is] = "null"

status Object No

optional, enumerated string filter
Status of the migration. Possible values are : moved_in, moved_out, moving_out.
Supported operators : is, is_not, in, not_in

Example → status[is] = "MOVED_OUT"

entity_type Object No

optional, enumerated string filter
Entity Type of the record. Possible values are : customer, subscription, invoice, credit_note, transaction, order.
Supported operators : is, is_not, in, not_in

Example → entity_type[is] = "customer"

offset String No

Determines your position in the list for pagination. To ensure that the next page is retrieved correctly, always set offset to the value of next_offset obtained in the previous iteration of the API call.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.