Overview

Get Personalized returns offers selected and ranked for a specific user on a wall. Display them in returned array order. Use Get Progress for event completion and credit status.

Hard user or IP restrictions return HTTP 403. A successful response with banned: true instead indicates a soft missing-credit-report restriction and can still contain offers. Offers marked wall_hidden remain in the response; exclude them from browse sections while retaining them where needed for progress views.

How It Works

1. Send a GET request to /api/v1/users/{user_id}/personalized, with the wall ID and requested numoffers. URL-encode the actual user ID in the path.

2. Pass the user’s actual device: desktop, ios or android. Omitting it selects desktop, including for mobile browser requests.

3. For a server-side request, pass the user’s ip. A direct browser request uses the caller’s IP by default.

4. Display eligible offers in returned order and handle the documented restriction flags and errors.

Request a fresh user-specific list when it is needed. numoffers accepts 1 through 500 and is required unless requesting a specific offer_id. The legacy /hotoffers_v3_api.php URL remains available with uid in the query. No API key is required or validated.

Use Cases

• Render an offer list selected for a user’s eligibility and history.

• Preserve RevU’s returned ranking in your app or game.

• Handle hard user/IP restrictions and soft support restrictions distinctly.

• Combine personalized discovery with event history from Get Progress.

API Key

No API key is required. You identify the request with your wall ID and user ID.