Skip to main content

​
Juno API

Juno provides a REST API for programmatic access to your organization’s data. Use it to connect BI tools, HR systems, and custom workflows to Juno.

API & MCP reference

Full endpoint reference with request and response examples, plus Juno MCP server setup.

​
Authentication

Every request needs a personal access token in the Authorization header:
To create a token, go to Admin → Security → Developer Settings and select Generate Personal Access Token. You need the IT Admin role to generate a token. Each token carries scopes that limit what it can do. Leave Connect AI assistants (MCP) unselected — that option creates an MCP access token, which works only with the Juno MCP server and is rejected by this API.
Treat tokens like passwords. Never share them or put them in client-side code. REST API tokens don’t expire, and you can’t revoke them yourself. If an API token is exposed, contact Juno support to replace it. MCP access tokens are different: an Admin with the IT Admin role can revoke them directly in Developer Settings.

​
Available endpoints

All endpoints live under /api/v1/public-api. Search endpoints accept a common query body — filters, limit, skip, sort, and select. See the API reference for filter fields and examples.

​
Rate limits

The API enforces rate limits to keep the platform stable. Limits are the same on every plan: a request returns at most 1,000 records, except POST /xapi/.search, which returns up to 10,000.
  • Webhooks — push data from Juno to your systems when an Automation runs.
  • xAPI — how Juno records learning activity as xAPI statements.
  • Juno MCP server — connect AI assistants to Juno.
The Juno API is primarily designed for integration partners and enterprise customers. API access is included on all plans.
Last modified on October 7, 2026