Apple's unique transaction identifier for the purchase to be transferred. This ID is used to identify the purchase in Cleeng's system.

IP address of the customer who requested the transfer. This information will be stored in the user's profile as the IP address of their latest activity. Accepted: IPv4

The parameter is required in backend intergrations (with middleware) to ensure the correct customer IP address (address of their latest activity) is stored.

Can be used within both server-to-server and client integrations. Either a JWT or X-Publisher-Token header authorization is required, depending on how you integrate with Cleeng.
Please use JWT (Bearer) token to try out the endpoint in the API console in this documentation.

Can be used only within server-to-server integrations. Either a JWT or X-Publisher-Token header authorization is required, depending on how you integrate with Cleeng.

Correlation ID for the request, which is used to link the initial purchase registration or transfer request with the subsequent synchronization process. This ID is not used as the synchronizationId but is included in the response for tracking and correlation purposes.

It is recommended to provide a Correlation-Id for easier tracking of requests, especially if you need to correlate the purchase registration with other events or processes in your system. Ensure that the Correlation-Id is unique within the context of your specific client integration to avoid conflicts.

Version of the publisher's application making the API request.
This header helps you track which versions of the publisher's app are being used and how they interact with Cleeng API. It can be valuable in identifying compatibility issues, understanding the impact of app updates on API usage, and providing support for different app versions.

Unique identifier for the device making the request (if applicable).
This header is useful for tracking requests at the device level, especially in mobile app integrations. It can help you identify issues related to specific devices, analyze user behavior across devices, and gather insights into device-specific usage patterns.

Specifies the type of device the request is coming from.
This header provides additional context about the device making the request, beyond just its unique ID. It helps you categorize devices (e.g., "iPhone 13", "Samsung Galaxy S21", "Web Browser") and identify potential issues or trends related to specific device types.

This information can be particularly useful for debugging, as it allows you to narrow down issues that may be specific to certain device models or types. It also helps in understanding user behavior and preferences across different device categories. Example: Apple TV

Specifies the action performed by the user in the publisher's application.
This header provides additional context about the user's actions within the app, such as "Purchase", "Restore Purchase", "Updating Plan", "Content Access", etc. It helps you understand user behavior, track specific actions that trigger API requests, and analyze usage patterns based on user actions.

By capturing user actions in the app, you can gain insights into user engagement, preferences, and interactions with your API. This information can be valuable for optimizing the user experience, tailoring content recommendations, and improving app performance.