Skip to main content
ModernLoop exposes a Platform API for integrations, automation, and AI agents. Use the REST API for direct HTTP calls, or connect an MCP client for tool-based agent workflows.
Most REST endpoints are currently in beta and may change without notice. See individual endpoint pages in the API Reference tab for stability tags.

​
Base URL

All requests use https://api.modernloop.io.

​
REST API

The REST API lets you list, read, and update recruiting and scheduling data in your ModernLoop organization.

​
Authentication

Send a ModernLoop API token as a Bearer token:
Tokens are scoped to your organization and act on behalf of the user who created them. Grant only the read and write scopes your integration needs.

​
Resources

The API covers these areas. See the API Reference tab for request and response schemas.

​
Conventions

  • Resource IDs use typed prefixes such as can_ (candidate), app_ (application), job_ (job), and usr_ (user).
  • Field names use lower_snake_case.
  • Timestamps are ISO 8601 in UTC.
  • List endpoints use cursor-based pagination. Pass the cursor query parameter from pagination.next_cursor to continue the same filtered result set.

​
Errors

Failed requests return a JSON envelope with an error object containing a machine-readable error.code, a human-readable error.message, and an optional error.docs_url.

​
MCP server

ModernLoop also provides a Model Context Protocol (MCP) server over Streamable HTTP. MCP exposes scheduling operations as tools that AI clients such as Claude Code, Codex, and Cursor can call directly. MCP connections use OAuth 2.1 with PKCE, or a static API token in the Authorization header. The read-only and read-write endpoints use separate OAuth resources. See ModernLoop MCP for client setup, toolsets for endpoint selection, and tools for the full tool reference.

​
Support

Questions about the Platform API? Contact support@modernloop.io.