Integrate RecoMind in minutes. Search, recommendations, chat, analytics, and customer intelligence — all through a single REST API.
https://api.recomind.ioAll API requests require authentication via the Authorization header. There are two authentication methods:
For server-to-server API calls (search, recommendations, chat, events).
Authorization: Bearer rm_prod_...For dashboard endpoints (analytics, keys, billing). Obtained via email code login.
Authorization: Bearer eyJhbG...Endpoints marked as Public do not require authentication.
Every search, recommendation and chat endpoint takes two identifiers, and both are optional.
session_idGroups one visitor's calls into a single browsing session. Omit it and the API generates one and returns it in the response — keep sending that value for the rest of the visit so search, recommendations, chat and the events they produce line up.
user_idYour identifier for a signed-in customer. Send it once they log in and their history follows them across devices. Leave it out for anonymous traffic: recommendations fall back to the store-wide popularity list rather than failing.
Send the same user_id on events and in /v1/users/import — that is the join that turns anonymous activity into a customer profile.
Let's have a virtual coffee and discuss how RecoMind can help.
Contact Sales