Ok Ru Odnoklassniki (OK.ru) API

Name: Odnoklassniki (OK.ru) API
Brand: Odnoklassniki (OK.ru) API
Availability: InStock

✓ Official Vendor SpecSocial MediaSocial Managementoauth220 EndpointsREST

For Agents

Read OK.ru user profiles, friends lists, and group metadata for social-listening and community-management workflows.

Install Jentic One Beta

Connect the Odnoklassniki (OK.ru) API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Odnoklassniki (OK.ru) API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Odnoklassniki (OK.ru) API.

Retrieve the currently logged-in user's profile and ID

Fetch profile data for a batch of user IDs in one call

List a user's friends and detect mutual connections

GET STARTED

Start building with Odnoklassniki (OK.ru) API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Odnoklassniki (OK.ru) API for, with concrete tasks.

★ Social login profile import

When a user signs in with OK.ru, fetch their profile via /api/users/getCurrentUser and getInfo to populate the local account record with display name, avatar, and verified-email flag. The API returns enough fields to skip the standard profile-completion step, reducing onboarding friction for Russian-speaking audiences.

After OAuth callback, call /api/users/getCurrentUser to retrieve the user's UID then /api/users/getInfo to fetch display name, gender, and locale

Friend graph import for invitations

Apps with social features import a user's OK.ru friends list to suggest in-app connections or send invitations. The friends endpoints expose UIDs that can be cross-referenced against existing app users, and the user-info endpoint enriches the matches with display data.

Fetch the logged-in user's friend UIDs and resolve them to display names with /api/users/getInfo in batches

Group community management

Community managers running OK.ru groups read group metadata to verify category, member count, and access settings, and confirm membership before posting moderation tools or analytics. The group endpoints provide a programmatic alternative to the OK.ru admin UI for routine checks.

Retrieve the metadata for an OK.ru group by its group_id and report category, type, and member count

AI agent social profile lookup via Jentic

An AI agent answering 'who is this OK.ru user?' uses Jentic to call getInfoBy and resolve a profile URL or numeric UID into a structured profile record. The agent searches Jentic for the lookup intent, loads the schema, and executes through OAuth credentials managed in your Jentic One instance.

Search Jentic for 'OK.ru get user info', load the schema, and execute getInfoBy for a user-supplied profile reference

Key Endpoints

20 endpoints — odnoklassniki (ok.

METHOD

PATH

DESCRIPTION

GET

/api/users/getCurrentUser

Get the current logged-in user's UID

GET

/api/users/getInfo

Fetch profile data for a list of UIDs

GET

/api/users/getInfoBy

Resolve a profile URL into a UID and profile data

GET

/api/users/isAppUser

Check whether a UID has installed the app

GET

/api/users/hasAppPermission

Check whether a UID has granted a specific app permission

GET

/api/users/checkFlag

Check an account flag value

GET

/api/users/getCurrentUser

Get the current logged-in user's UID

GET

/api/users/getInfo

Fetch profile data for a list of UIDs

GET

/api/users/getInfoBy

Resolve a profile URL into a UID and profile data

GET

/api/users/isAppUser

Check whether a UID has installed the app

GET

/api/users/hasAppPermission

Check whether a UID has granted a specific app permission

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your OK.ru OAuth client credentials and per-user tokens are stored once, encrypted, by your own Jentic One instance, which mints and refreshes tokens and injects them at execution time. The client secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get OK.ru group info' or 'look up a user', and Jentic returns the matching operation with its parameters typed in the input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Odnoklassniki (OK.ru) API through Jentic.

What authentication does the OK.ru API use?

The API uses OAuth 2.0. Apps register on apiok.ru, redirect users through the OAuth flow, and call endpoints with the resulting access token. Through Jentic, OAuth client credentials are stored encrypted in the vault and tokens are refreshed automatically, so the raw client secret never enters the agent's context.

Can I look up a user's profile with the OK.ru API?

Yes. /api/users/getCurrentUser returns the logged-in user's UID, /api/users/getInfo accepts a list of UIDs and returns profile fields, and /api/users/getInfoBy resolves a profile URL into a UID first. Choose the endpoint that matches the input form you have.

What are the rate limits for the OK.ru API?

OK.ru applies per-app and per-user rate limits that vary by app tier. Limits are not exposed in the spec but are documented on apiok.ru. Treat 429 and 'too many requests' responses as a backoff signal and batch UID lookups (getInfo accepts arrays) to reduce call volume.

How do I get the current user's friends through Jentic?

Search Jentic for 'OK.ru friends list', load the schema for the friends operation, and execute with the access token bound to the logged-in user. The response contains UIDs, which you can then resolve via /api/users/getInfo for display names.

Can I check whether a user has installed my OK.ru app?

Yes. /api/users/isAppUser returns whether a UID has installed the calling app, and /api/users/hasAppPermission checks specific permissions like photo or messaging. These are useful before calling endpoints that require app-user consent.

Can I limit what my agent is allowed to do with the OK.ru API?

Yes. Because the OK.ru read endpoints carry their targets in query parameters rather than the URL path, Jentic One scopes access by operation, and since you self-host it your own rules decide which of the 20 reads the agent may call. You can allow just getCurrentUser and getInfo for a profile-lookup agent, add the friends and group-metadata reads for a community-management agent, and the agent can call nothing outside that allowed set. Your OAuth client credentials stay in your Jentic One instance and are injected at execution time, so the agent never sees the client secret.