# VKit Platform API > VKit is the creator platform behind a creator's link-in-bio page, their > Instagram comment-to-DM automations, their content studio and their community. > This API acts on ONE creator's workspace, named by the credential. ## Get in There are two faces here and they take different credentials. Acting FOR A CREATOR (their page, posts, automations, community): - OAuth 2.1 + PKCE. Discovery: https://api.vkit.app/.well-known/oauth-authorization-server It advertises `registration_endpoint`: register yourself at `POST https://api.vkit.app/v1/oauth/register` (RFC 7591) with a `client_name` and your `redirect_uris`, store the `client_id`, then run the authorization-code flow. Public client, `token_endpoint_auth_method: none`, S256 only. - Or a workspace API key (`vka_…`) for your own workspace. Booking or buying FROM a creator, for a customer: - A partner key (`vkx_…`) issued by VKit. There is no OAuth flow for a partner — a partner uses an API key issued by VKit rather than a creator's authorization. Ask developers@vkit.app. - Or a creator credential carrying `commerce.book`, for that creator's own shop. Either way: `Authorization: Bearer `. A creator token names its workspace; a partner key names none, and the creator is the handle in the URL. There is no tenant header. ## Contracts - OpenAPI: https://api.vkit.app/openapi.json - Base URL: https://api.vkit.app/v1 - MCP (streamable HTTP): https://api.vkit.app/mcp — metadata at https://api.vkit.app/.well-known/mcp.json - Docs: https://api.vkit.app/ ## Scopes profile.read, links.write, page.write, instagram.connect, automations.write, posts.write, posts.schedule, analytics.read, community.manage, broadcasts.write, commerce.book. A creator grants a subset; ask for what you will use and nothing more. A partner key carries no scopes: it can reach the commerce routes and nothing else. ## Buying and booking - `GET /v1/creators/{handle}/services` — what a creator can be booked for, and `payment.network_id`, the Stripe profile to issue a shared payment token against. - `GET /v1/creators/{handle}/availability` — open slots, with a stable `slot_id`. - `POST /v1/bookings` — book and pay in one call. `GET|PATCH|DELETE /v1/bookings/{id}`. - `GET /v1/creators/{handle}/products`, `POST /v1/orders`. - Pass `Idempotency-Key` on every write. A retry without one is a second appointment and a second charge. ## What this API will not do - It will not publish a page, turn on an automation, or post to a social platform as a side effect of anything. Each is its own explicit call. - It will not report a publish that did not happen. `GET /v1/posts/targets` tells you which platforms can actually publish before you promise one. - It will not connect an Instagram account for you. `POST /v1/instagram/connect` returns a URL for the creator to open. - It will not confirm a booking nobody has. A taken slot answers `409 slot_unavailable`; a declined card answers `402 payment_declined` and nothing is held. A creator who has not opted in to agent bookings answers `403 agent_bookings_disabled` — do not retry that one. ## Start here `GET /v1/capabilities` — what this workspace can do right now and what to do next.