01
Catalog contract
Agree item identifiers, attributes, availability updates, import cadence, and how removed items are handled.
For developers
Recommendations belong in your product.
Explore the data and API patterns behind RankNexa’s integration approach. Clear inputs, contextual ranking, and useful feedback loops.
Book a demoA clear integration conversation
Four interfaces.
One discovery workflow.
The API direction covers catalog ingestion, event tracking, recommendation retrieval, and re-ranking. Use this example to discuss payload shape and product fit.
- Stable item and session identifiers
- Placement and context in each request
- Ranked identifiers returned to your product
- Outcome events for evaluation
This is an illustrative API concept. The example does not call a public service. Confirm endpoint availability, authentication, schema, and deployment scope with RankNexa.
POST /v1/recommendationsContent-Type: application/jsonAuthorization: Bearer <YOUR_API_KEY> { "placement": "product_detail", "user_id": "demo_user_42", "session_id": "demo_session_12", "context": { "item_id": "sku_1048", "locale": "en-IN" }, "limit": 4}Illustrative API example · schema subject to implementation
Before you integrate
Define the contract, not just the request.
02
Event contract
Choose relevant event types, timestamps, placement attribution, consent requirements, and a policy for missing identifiers.
03
Serving contract
Define request context, response shape, authentication, error handling, fallback behavior, and operational expectations.
04
Evaluation contract
Establish a baseline, outcome measures, guardrails, and the data needed to compare ranking strategies.
Let’s find your starting point
Great catalogs.
Even better discovery.
Bring your product, your catalog, and your biggest relevance question. Let’s talk about what a better experience could look like.
Book a demo