For information about how REST API works, see rest main page.
Read-only view of the interests Personyze has inferred for each user — the categories, tags and topics they engage with, scored by relevance. This is the raw material behind interest-based targeting and recommendations, and it is often the most useful thing to export into a CRM or an email tool.
The endpoint URL is:
app.personyze.com/rest/user_interestsGET only. One row per user, value and class.
Columns
| Column | Description |
|---|---|
user_id |
The user this interest belongs to. Indexed — query by it. |
class |
Which kind of interest this is: the category, tag or attribute family the value came from. |
value |
The interest itself, e.g. a category name or a tag. |
rank |
Relevance score. Higher means stronger interest — sort by this. |
n_times |
How many times the value was observed for this user. |
time |
When it was last observed, Unix timestamp. |
Select example
A user's top interests:
curl 'https://api:FD09908F25BECB09D78EBEA1DADFB618651F612D@app.personyze.com/rest/user_interests/where/user_id=123/order_by_desc/rank/limit/10'Only one class of interest:
curl 'https://api:FD09908F25BECB09D78EBEA1DADFB618651F612D@app.personyze.com/rest/user_interests/where/user_id=123&class=category/order_by_desc/rank'Performance
Always constrain by user_id. This table has one row per user per interest, so it is large; scanning it by value or class alone is a full scan and will be refused or truncated — see errors and limits.