Skip to content
Median
Esc
↑↓navigate↵open⌘Jpreview

Get the config

Your organization’s name and the agent that answers. Renaming the agent in the dashboard is reflected here.

GET/config
Authorization
AuthorizationBearer token · headerrequired
A MEDIAN_KEY from Settings under API. It starts with `median_key_` and stays on your server. The tool endpoint routes also accept an OAuth access token (`median_oat_`) from `median login` or an MCP client, acting as the person who approved it. The messaging routes accept only a Median key.
Responses
200The organization and its agent.
orgNamestringrequired
agentAgentrequired
Who answered. Covers both the AI and your team.
Show properties
kindstringrequired
Allowed:aihuman
namestringrequired
avatarUrlstring | nullrequired
401`missing_api_key`: no bearer token. `invalid_api_key`: the key matches no organization or was revoked. `publishable_key`: a `median_pk_` key was sent. An OAuth access token is refused here with `invalid_api_key`.
errorobjectrequired
Show properties
codestringrequired
Branch on this rather than on the message.
messagestringrequired
429The organization's API allowance for this class of request is used up. Wait the `Retry-After` header's seconds. Limits depend on the plan. See [rate limits](/api/errors-and-limits#rate-limits).
errorobjectrequired
Show properties
codestringrequired
Branch on this rather than on the message.
messagestringrequired
Request
curl -X GET "https://api.median.sh/v1/config" \
  -H "Authorization: Bearer YOUR_TOKEN"
Response
{
  "orgName": "Acme",
  "agent": {
    "kind": "ai",
    "name": "Median AI",
    "avatarUrl": null
  }
}