
Connect Mistral AI to Lutril
Lutril connects to Mistral with an Admin API key and reads your organization users with their roles and which products their seat is paid for. Access is time boxed on the ROLE: a grant adds one organization role and the deadline removes exactly that role. Lutril neither creates nor deletes a Mistral user, because deleting is the only account removal Mistral offers and it destroys the account rather than suspending it, so an account created for a grant could never be taken back at its deadline.
Access requested
- The key is not scope based. It has to be an ADMIN API key: a standard Mistral API key is rejected by every admin endpoint.
- The Admin API is available on Enterprise plans only, and access is not self serve.
Setup steps
- 1
Check your plan first. Mistral's Admin API is available on Enterprise plans only and access is not self serve, so on any other plan there is no key to create. Contact your Mistral account team or sales to have it enabled.
Admin API authentication - 2
With Enterprise account admin access, open the Admin Panel and go to API keys in the enterprise section.
Open the Mistral Admin Panel - 3
Select Create key, give it a name, choose the organization, and optionally set an expiry.
- 4
Copy the key straight away. Mistral shows it once.
- 5
In Lutril, connect Mistral AI and paste the Admin API key. Lutril sends it as the x-api-key header.
- 6
To time box Mistral access, set the access levels on the Mistral AI app in your catalogue to member, billing_manager and organization_admin. Those are Mistral's own role names, so what somebody requests is exactly what they get.
Roles and permissions - 7
A grant adds exactly one role and keeps every other role the person holds. The deadline re-reads the user and removes only the role the grant added, so a role somebody else granted inside the window survives.
- 8
Creating and removing a Mistral account both stay manual steps, and that is deliberate. Mistral's API can only delete a user, which destroys the account rather than suspending it, and Lutril will not call a destructive endpoint at a deadline. A connector that could create an account but never remove it would be worse than one that does neither: the person would keep the access forever while the system reported it revoked. So invite people in the Mistral console, and let Lutril time box the role, which is the part that actually matters: an organization admin can mint API keys and change billing.
- 9
Lutril reads the roster tolerantly, because Mistral documents the request format for these endpoints without documenting the response. Anything Lutril cannot find it reports as absent rather than guessing, so an unrecognised role is shown as itself and a missing date stays blank.
Where to create it
Official docs
Sign in to Lutril to connect Mistral AI, or book a demo and we set it up with you. No slides.