Programmatic access to a Jira site’s Mria CRM data under the path /v1: leads, contacts, companies, deals, products, their activities, links and custom fields, plus reference data and metrics.
Browse every endpoint in the interactive API reference, with parameters, request bodies and response schemas.
Authentication is Atlassian OAuth 2.0 (3LO). There are no API keys. Every call runs on behalf of a real Atlassian user, with that user’s CRM permissions.
Setup and reference #
- Setup. Enable the API and create the 3LO integration.
- Authorization with curl. The 3LO handshake as plain HTTP, with the errors.
- Reference. Every endpoint, searchable, plus the OpenAPI spec to download.
- Example Postman. Import the spec and call the API.
- Example Node.js. The same flow in one file of code.
- Paging, Filters, Errors and Limits. How lists page and filter, the error envelope, the sizes and rates.
- Attaching Files. Upload, list, download and delete the files on a record.
Extended list responses #
List endpoints can return full record details rather than a trimmed summary, and records now carry their created and updated timestamps.
This is what makes incremental syncing practical: with an updated timestamp on every record you can pull only what has changed since your last run, instead of re-reading the whole collection and diffing it yourself. It also means a single list call can populate a downstream system without a follow-up request per record.
The OpenAPI spec is the authoritative reference for exactly which fields each endpoint returns and how to request the extended form. Check it against the version deployed on your site — the API is actively developed, so shapes can change.
Files #
Files can be attached to Leads, Deals, Contacts and Companies, listed, downloaded and deleted — the same files as the record’s Files tab. An upload is three calls: start, send the bytes to a one-time URL, confirm. See REST API: Attaching Files.
Company and Contact types #
GET /v1/recordTypes?entity=COMPANY (or CONTACT) lists a type list in display order; on the Companies list the first type carries isDefault. Companies and Contacts return their type — a Contact also says whether it is inherited from its Company — take a typeId when created, and can be searched by typeIds. See Company & Contact Types.
How-to guides #
Complete, worked integrations built on the API. Each one stands on its own and names the setup it needs.
- Zapier: Lead Capture. A web form submission becomes a Lead in Mria CRM.
- Zapier: Mailchimp Emails to Notes. An email campaign is logged as a note on each matching contact.
- Migrating Activity History from Salesforce. Calls, emails, meetings, tasks and notes are written to the migrated records, with a sample script.
- Getting Mria CRM Data into Power BI. A scheduled, read-only export feeds a Power BI model, with the export script and a template.
AI clients #
For ChatGPT, Claude or another AI assistant, you do not need the REST API: Mria CRM also exposes an MCP server that Atlassian hosts, switched on per site by an Atlassian admin and used under each person’s own CRM permissions. See Mria CRM MCP server.
References #
This API is supported and actively developed, so it can change without notice. It builds on Atlassian’s Forge App REST APIs (Preview). Send feedback to the Mria CRM team.