Skip to main content
The PRIXO REST API gives you programmatic access to the core capabilities that power prixo.ai — restaurant search, live delivery price comparison, AI-assisted chat, and trending query data. Every JSON endpoint can be called from scripts, dashboards, or any tool that can make HTTP requests. Community price snapshot submissions are handled through the PRIXO web interface rather than this API.

​
Base URL

All API requests go to:

​
Response format

Every successful response returns a JSON body. There are no XML or plain-text responses. Set the Content-Type: application/json header on all requests that include a body, and expect Content-Type: application/json on every response.

​
Authentication

PRIXO uses session cookies. Most read endpoints are fully public — you can call them without any credentials. Write endpoints and personalized features require a signed-in session cookie. See the Authentication guide for setup details.

​
Available endpoints

​
Rate limits

PRIXO enforces per-user rate limits on high-traffic and write endpoints to ensure fair access for everyone. Limits are tracked by authenticated user ID or IP address. When you exceed a limit, the API responds with HTTP 429 and the following JSON body:
PRIXO’s rate limiter is fail-open by design. If the rate-limiting service experiences a transient outage, requests are allowed through rather than blocked — your integration will never be hard-stopped by an infrastructure hiccup.

​
Error format

All errors follow a single, consistent shape:
The error field contains a human-readable string describing what went wrong. Pair it with the HTTP status code to handle errors programmatically.

​
Common status codes

For 500 errors, wait a moment and retry with exponential back-off. If the problem persists, reach out via the feedback endpoint or through prixo.ai.