Introduction

Meridian HR is a multi-tenant HRMIS built for African organisations. These docs cover the two programmatic ways to integrate with it:

a REST API secured by org-scoped API keys, and
an MCP server that lets AI agents work directly with employee, leave, and payroll data.

Both share the same permission model. An API key is an OrgMember with the same RBAC as a human user — it sees exactly what its role allows, and nothing more.

What you can do

REST API

Create an API key, set the X-Org-Id header, call any endpoint a member with the same role could call.

MCP Server

Run the Meridian MCP server alongside Claude, Cursor, or any MCP-capable agent. Tools are filtered by your permissions.

Base URLs

Environment	URL
Production	`https://api.meridianhr.co`
Staging	`https://staging.meridianhr.co`

Conventions

All requests are JSON. Content-Type: application/json is required for POST, PUT, and PATCH.
Every org-scoped request requires the X-Org-Id header. See Authentication.
Money is serialised as a decimal number with up to 4 decimal places (NUMERIC(19,4) in storage).
Dates and timestamps are ISO-8601 in UTC.
Errors follow the same envelope across every endpoint:

{
  "error": {
    "code": "validation_error",
    "message": "salary must be greater than 0",
    "details": { "field": "salary" }
  }
}

Need help?

Open a ticket at support@meridianhr.co or reach the team on docs.meridianhr.co.