Odnoklassniki (OK.ru) API

Name: Odnoklassniki (OK.ru) API 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.

Quickstart

Get started with Odnoklassniki (OK.ru) API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get an ok.ru user profile"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Odnoklassniki (OK.ru) API 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

Check whether a user has installed an app or granted a permission

Read group metadata, membership, and category information

GET STARTED

Start building with Odnoklassniki (OK.ru) API API

Explore with Jentic

View OpenAPI Spec

Use Cases

Patterns agents use Odnoklassniki (OK.ru) API 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 the Jentic vault.

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 though Jentic?

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

Credential isolation

OK.ru OAuth client credentials and per-user access tokens are stored encrypted in the Jentic vault. Tokens are minted and refreshed by Jentic; the agent never holds the client secret directly.

Intent-based discovery

Twenty endpoints across users, friends, and groups are easy to miss in OK.ru's docs. Agents search Jentic by intent (for example 'get OK.ru group info') and Jentic returns the matching operation with parameters typed.

Time to first call

Direct integration including app registration, OAuth flow, and method-style endpoint quirks: 1-2 days. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

VK API

Russia's other major social network with a similar profile, friend, and group API surface

Choose VK when the audience skews younger and urban; OK.ru tends to skew older and regional. Many integrations support both.

Alternative

Facebook Graph API

Western social graph alternative when the audience is global rather than CIS-region

Use Facebook Graph for Western audiences; use OK.ru for CIS-region users where OK is dominant.

Complementary

Instagram Graph API

Pair OK.ru community management with Instagram for a multi-platform social presence

Use Instagram for image-led publishing; OK.ru complements with the Russian-speaking community-and-friends graph.

FAQs

Specific to using Odnoklassniki (OK.ru) API 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.