Skip to content

Developers · VOR API 2.5.43

One API for editors and their AI agents

VOR API is the programming interface of VOR Studio. Everything an editor does in Studio – drafts, translation, preview, scheduling, publishing, media – an agent can do through the same API, with exactly the rights an administrator gives it.

Who am I?GET /studio/api/jag
$ curl https://your-domain.com/studio/api/jag \
    -H "Authorization: Bearer $VOR_AGENT_KEY"

{
  "ok": true,
  "release": "2.5.43",
  "vem": {
    "typ": "agent",
    "roll": "agent",
    "sektioner": ["mode", "skonhet"],
    "sprak": ["sv", "en"],
    "publicera": false,
    "schemalagga": false
  }
}
84operations in the API
72endpoints, one specification
23tools in the VOR Studio connector
11tools in the VOR Insights connector

Live · counted from the specification and the connectors each time this page is served

How an agent gets access

Agents never get more than they are given. The default is a writer who hands in drafts; a person decides what goes live.

  1. An administrator creates the agent

    In VOR Studio › Agents. The key is shown once, to the administrator.

  2. The agent sends its key

    In every request: Authorization: Bearer mms_…

  3. It starts with drafts

    Publishing and scheduling only in the sections, templates and languages the administrator allows.

  4. Every save is a revision

    Language versions are immutable revisions. Two writers at once get a 409 instead of overwriting each other.

Connect from Claude or ChatGPT

No keys in the chat. Claude signs in with a button (OAuth with PKCE), as the person using it; a ChatGPT Action gets its agent key in the GPT's settings.

Claude · MCP

Two connectors: VOR Studio for writing and publishing, VOR Insights for traffic, revenue and the assignment queue.

https://your-domain.com/studio/mcp
https://your-domain.com/management/mcp

VOR Studio: 23 toolsVOR Insights: 11 tools

ChatGPT · Actions

A ready selection of the operations a writing agent needs – ChatGPT Actions take at most 30. Publishing and status changes are marked so ChatGPT asks before it runs them.

https://your-domain.com/studio/api/openapi-chatgpt.json

29 operationsSign-in: agent key

What's in the API

Every operation, grouped the way an editorial team works. The numbers are operations. See all of them →

20Content and revisions

Create drafts, write language versions as immutable revisions, check before publishing, comment and compare.

15Preview and publishing

Preview with the site's own rendering, share time-limited links, publish now or on a schedule, and follow every release.

5Translation and jobs

AI translation as drafts – one article or sixty at a time – with job status to poll.

9Media library

Upload images, keep credits and rights, write alt text per language and see where each image is used.

6Tags, categories and people

Suggest and set tags, create tags for names and read the site's dictionary of people.

8Assignments and ideas

The shared queue between editors and agents, and the ideas from media monitoring.

4Commerce links

The link monitor and the site's outbound links to affiliate programmes.

17Account, rules and administration

Who you are, the editorial handbook, templates and sections – and, for administrators, agents, roles, settings, log and export.

Errors a machine can act on

Every error says which field, in which language, why – and what to do about it. Field names and messages are in Swedish, as in Studio.

falt
the field
sprak
the language version
orsak
what went wrong
atgard
how to fix it
Checked before publishingPOST …/validera
{
  "ok": false,
  "fel": [{
    "sprak": "en",
    "falt": "ingress",
    "orsak": "Ingress saknas",
    "atgard": "Skriv en ingress"
  }],
  "varningar": []
}