Platform documentation
Pereval connects dating apps and websites into one network. Your user stays with you, but sees people from other apps, likes them and chats with them — with translation if their languages differ. Basic integration and exchanging profiles, ordinary likes, matches and messages are free. Additional services are optional.
We are just launching the network: external profiles may be few or absent. If you join first, cross-platform introductions become possible once other platforms join. You can test integration in the sandbox and prepare for growth. We are preparing optional-service bonuses for early participants; amounts and terms will be published separately. For founding platforms.
Where to start
Pick the start that matches the product. It stands alone: what to store, which requests, and when the integration is done. The full rules and every field are in the sections below and in the API reference.
| Your product | Start |
|---|---|
| an app where a person flips through profiles one by one | Swipe app |
| a site with filters and pages of profiles | Search site |
| a bot, and you have no webhook URL | Bot |
| you want to test the API and sandbox with curl | Test the API in the sandbox |
| you have not chosen how to connect yet | Ways to integrate |
| an AI agent will write the integration | For AI agents — the agent needs this page and the start for the product |
From application to launch
- Apply. We review the platform by hand and open the dashboard for you.
- Test the API in the test environment. Issue a test key, send a
pingand run the sandbox scenario. The 15-minute API check confirms that requests and events work; it is not a finished integration in your product. - Build the user flow into your product. Add opt-in consent, profile sync, the network feed, and handling for likes, matches, messages and events. Choose a start for an app, website or bot.
- Pass the checklist and enable the live environment. Verify consent, deletion, event signatures and user-facing notices, then issue a live key in the dashboard. See the full testing checklist.
What to build into your product
- User consent. A “Show me in the Pereval network” toggle in profile settings, off by default (and, optionally, “Open to chatting in other languages”). Without consent turned on, the profile is not sent to the network.
- Sending profiles. When a person turns on participation or changes their profile —
PUT /v1/members/{your_user_id}. For the first upload, batches work best —PUT /v1/members. - Feed. Show people from the network alongside your own:
GET /v1/members/{id}/feed. Each card shows which app the person is from. In a swipe app, a skip without a like is a dislike. On a search site, pages use the cursor, and a dislike is only an explicit rejection. - Likes, matches, messages — a few requests plus receiving events: through webhooks or with
GET /v1/events.
The effort depends on how your product is built. The minimum user flow includes profiles and consent, the feed, likes and skips, messaging, and event handling.
Network principles
- The user is yours. The network does not talk to your users directly, does not collect their contacts and does not poach them. The whole interface is yours.
- Consent only. The network includes only people who turned on participation themselves. Chatting in other languages is a separate consent.
- Immediate deletion. One request erases a person’s profile from the network; the people they talked to keep the chat history without the name and photos.
- Pause the connection. Suspension hides the platform’s profiles from discovery and prevents new likes and messages in both directions. History is not deleted and event delivery is paused. This is not deletion of user data; profile deletion uses a separate request.
- Free basic integration. Boost, superlike, incognito and rewind are optional network services, starting at zero RUB. Platforms set their own user-facing offers. Rules against fake profiles and harvesting apply to everyone; no ordinary-growth tariff is set.
- Open protocol. The specification is public; changes are versioned and announced in advance, breaking ones 60 days ahead.
Protocol version
This documentation pins specification 1.0.0 from the agreed network release. It does not confirm that this version is already deployed on the public API: check GET /v1/capabilities with the target environment’s key before enabling features. A 404 means this runtime contract is not supported yet, not that every feature is available.
The protocol includes profiles and consent, nearby and worldwide feeds, likes, super likes, dislikes, matches, and events by webhook or by request. Translation depends on a configured service; failures leave the original available. Production video is disabled until frame moderation exists: when videos: false, do not submit nonempty videos. Capabilities describe configuration, not external service health; /readyz only checks database availability. There are no calls yet. The full list is in the changelog.