API keys and authentication for MJX CRM

Every call to the MJX CRM API and the MCP server carries an API key. In Pathshala, the key itself says which institute you are — the address you call and the body you send cannot change that.

#What does a key look like?

A key starts with mjx_live_ followed by 40 letters and digits, for example:

mjx_live_AbCdEfGhIjKlMnOpQrStUvWxYz0123456789AbCd

The list on the Integrations page shows only its first 13 characters (mjx_live_AbCd…) so you can tell keys apart.

#How to make an API key

1. Sign in as the Owner or an Admin.
2. Open the Integrations page and scroll to API keys.
3. In Name it (where it will be used), type a name such as "Old ERP" or "Zapier".
4. In Can, pick Read and write or Only read.
5. Press Make a key.
6. Copy the key from the box that says "Copy this key now — it will not be shown again." Press Copy, then I have copied it.

#Scopes: read and write

A read-only key that tries to write gets 403 with: "This key is read-only. Make a key with "write" to add or change leads."

There is no delete scope. No key can delete a lead.

#How to send the key

Send it in the Authorization header as a Bearer token:

curl https://sunrise.pathshala.mjxtechnologies.com/api/v1/crm/me \
  -H "Authorization: Bearer mjx_live_…"

Or in the X-API-Key header:

curl https://sunrise.pathshala.mjxtechnologies.com/api/v1/crm/me \
  -H "X-API-Key: mjx_live_…"

If both are sent, the Authorization: Bearer header is used.

#What is checked on every call?

1. A key was sent. If not: 401 "Send your API key: "Authorization: Bearer mjx_live_…"."
2. The key exists and is not revoked. If not: 401 "That API key is not valid, or it was revoked."
3. MJX CRM is switched on for the institute. If not: 403 "MJX CRM is not switched on for this institute."
4. The institute is on MJX CRM Pro. If not: 403 "The API comes with MJX CRM Pro." (on the MCP server: "The MCP connection comes with MJX CRM Pro.")
5. For a write, the key has the write scope.

The Pro check runs on every request, not only when the key was made. A key keeps working the moment the institute is back on Pro.

#How to revoke a key

1. Find the key in the list.
2. Press Revoke.

The key stops working at once. The row stays in the list with "revoked" and the date. Revoking works on every plan, even after a move to Basic.

#Limits on keys

#Who can manage keys?

Only the Owner or an Admin. Anyone else gets "Only the owner or an admin can manage integrations." Making a key needs CRM Pro; on Basic the page shows a lock and the buttons are greyed out.

#Tips

• Name each key after the system that uses it. The "used" time tells you which keys are still alive.
• Use Only read for reporting tools and AI assistants that only need to look.
• The same key works for the REST API and the MCP server.

#Questions people ask