Platform API

Build something creators connect once and forget about.

Your client registers itself — no application form for a client id (RFC 7591, in the OAuth guide). The partner program is the step after that: a reviewed listing appears on a creator’s consent screen with your name and logo and without the “registered itself, not reviewed” line, gets a sandbox workspace, and shows on their Connected apps page afterwards, where they can see what you have been doing and cut you off in one click.

How it goes

  1. Register and build. POST /v1/oauth/register hands your client a client_id on the spot, as a public PKCE client. Build against it; creators can connect it today.
  2. Tell us what you built. Email [email protected] with that client id, the name creators will see, your logo, your homepage, your privacy and terms URLs, and the scopes you need with a line on why for each. A confidential (server-side) client that needs a secret is registered by us at this step; a browser, desktop or connector client takes no secret at all: PKCE is the proof, and a secret shipped in a client is a secret that has leaked.
  3. You get a sandbox workspace — a real tenant with real data shapes and no real creator in it — so you can exercise every path before a creator sees your integration.
  4. We review, and you go live. Review is mostly the consent screen: your name, your scopes, and whether what you do matches what a creator reading that screen would expect.

What we ask of you

Ask for less

Request only the scopes you call. An integration asking for all eleven is one creators decline, and one we will send back.

Never publish by surprise

Publishing a page, turning on an automation and sending a broadcast are each their own call, because each is visible to someone else. Do not chain them behind one creator action without saying so.

Handle revocation

A creator can cut you off at any moment, and their grant dies with their membership of that workspace. Treat 401 invalid_token as “ask again”, never as a retry.

Do not re-host their audience

analytics.read gives you summaries, never a follower’s personal details, and community.manage returns member counts before it returns member rows. Keep it that way in your own storage.

Be idempotent

Send an Idempotency-Key on every write. Creator credits are real money; a retry that generates a second carousel is a bill they did not agree to.

Say what you cannot do

If GET api.vkit.app/v1/posts/targets says a platform cannot publish, tell the creator that. Reporting a post that will never go out is the one thing that loses their trust for good.

Already a creator?

You do not need any of this to automate your own account. Make a workspace API key in Settings → Connected apps → Developers and start with the quickstart.