List the current announcements
The announcements.list_current operation: GET /api/v1/announcements/current in the REST API and the announcements_list_current tool in the MCP server.
GET
/api/v1/announcements/currentThe announcements Ownrecord shows at the top of the console right now (spec §39.1), most severe first: planned
maintenance, incidents, changes that need your attention. With orgId (an organization you belong to), the list
also has the announcements for that organization's plan; without it, only those for everyone. Messages are plain
text from Ownrecord staff.
At a glance
- REST:
GET /api/v1/announcements/current - MCP tool:
announcements_list_current - Operation ID:
announcements.list_current - Scope: Platform
- Permission:
account:read - Risk tier:
read - Dry run: Not supported
- Idempotency: Not needed (read only)
- Modes: Test and live
- Authentication: API key with the
account:readscope - Since: M12
Request
Query parameters
| Field | Type | Required | Description |
|---|---|---|---|
orgId | org_… ID | No | An organization you belong to. |
Response
200 OK with a JSON object:
| Field | Type | Description |
|---|---|---|
object | "list" | |
data | array of object | |
data[].object | "announcement" | |
data[].id | string | |
data[].message | string | Plain text from Ownrecord staff. |
data[].severity | one of info, warning, critical | |
data[].link | string or null |
Examples
Planned maintenance
HTTP
GET /api/v1/announcements/current
Authorization: Bearer or_test_…
Response (200):
JSON
{
"object": "list",
"data": [
{
"object": "announcement",
"id": "maintenance-2026-11-08",
"message": "Planned maintenance on Sunday, November 8, 02:00–02:30 UTC. Checkout and the API stay up.",
"severity": "info",
"link": "/docs"
}
]
}
Errors
| Code | HTTP status | When | What to do |
|---|---|---|---|
resource_not_found | 404 | orgId isn't an organization you belong to. | Check the ID and that your credentials are scoped to the right organization, entity, brand and mode. |
permission_denied | 403 | You aren't signed in as a person (API keys have no console). | Ask an organization owner or admin for a role or scope that allows this action. |
It can also return these common errors: validation_failed, api_version_unsupported, authentication_required, api_key_invalid, dry_run_not_supported, rate_limited, internal_error.