🌎Get offline LTV list

---

Overview:

This endpoint provides a list of objects related to specific app users and their Long-Term Value (LTV) score. The LTV score indicates the projected revenue a user will bring to an application over the entire time they use the app.

---

Request Method:

• Type: GET

---

URL:

https://0d634nkn4a.execute-api.us-east-2.amazonaws.com/development/get-ltv-list

---

Headers:

• x-api-key: Your API key for authorization (e.g., your_api_key).

• Content-Type: The type of the request body. Always set it as application/json.

---

Body:

{}

Note: The body currently seems to be an empty JSON object. Please ensure there are no parameters required for this API call. If there are, update this section accordingly.

---

Response:

The response will be a JSON array containing objects. Each object represents a user's LTV score and associated identifiers.

Example:

[
    {
        "remoteId": "D34DA17C-5337-4378-8425-A9266388E774.com.datonomy.tle.dot",
        "idfa": "00000000-0000-0000-0000-000000000000",
        "idfv": "A6043FEA-AA2A-42DA-923A-ADFB2E49348A",
        "ltvScore": 3,
        "bundleId": "com.datonomy.tle.dot",
        "date": "2023-08-31"
    },
    ...
]

---

Object Fields:

• remoteId (String): A unique identifier for the user associated with a specific application.

• idfa (String): Identifier for Advertisers. A unique ID for each iOS device, used for targeted advertising.

• idfv (String): Identifier for Vendors. A unique ID assigned by Apple to a specific vendor.

• ltvScore (Number): The Long-Term Value score of the user.

• bundleId (String): The identifier for the application bundle.

• date (String): The date associated with the LTV score, in the format "YYYY-MM-DD".

---

Usage Limits:

Make sure to include any limits on the number of requests that can be made to this endpoint within a certain timeframe, or any other rate-limiting or restrictions in place.

---

Additional Notes:

• Always ensure that the API key is kept secret and is not exposed to unauthorized users.

• This endpoint provides over 1000 items; hence, consider using pagination if the application consuming this API needs to handle a large amount of data.

---