Minuet offers a guided connector that handles the API access for you. Your Minuet administrator starts it from the FirstIgnite screen in Minuet, and a FirstIgnite team admin confirms it. It needs Minuet 20.0101 or newer.

FirstIgnite never asks for anyone's Minuet password, and no individual user needs their own Minuet login to use FirstIgnite.

Prefer to watch first? This two-minute walkthrough of the guided connector takes you from the FirstIgnite screen in Minuet to the confirmation in FirstIgnite. It was recorded on an earlier build, so the menu name and the endpoint count on screen have moved on since. The steps below are the current ones.

Check your Minuet version. In Minuet, click the logo chevron at the top left, choose About Minuet, and scroll to the bottom of the Help window.

The connector needs Minuet 20.0101 or newer. If you're on an older version, ask Inteum to upgrade you before you start.

One capability has its own floor on top of that:

You need two people. A Minuet administrator to set up access on the Minuet side, and a FirstIgnite team owner or admin to confirm the connection and turn features on. Neither can finish alone. This is the step teams most often get stuck on.

Ask your FirstIgnite contact to give the accounts that will use it the Inteum user permission. You can't do this yourself, and without it those people see nothing Minuet-related however the connection goes. It has a human turnaround, so start it now.

If you host Minuet yourselves, get the firewall work moving first. The first step of setup checks that FirstIgnite can reach your instance, and it fails until your network team has allowlisted us. See If you host Minuet yourselves below.

Pick the Minuet user the integration will run as. Whatever that account can see is what FirstIgnite can see. Use a dedicated service account rather than a real person's login. A person's account can be narrowed by an ordinary permission change or deactivated when they move roles, and either takes the integration down. Give it broad data access. The endpoint permissions and the user's own record permissions are two separate things, and both have to be right.

The account is transport, not a byline. Emails FirstIgnite logs back to Minuet are attributed to the person who actually sent them, not to the service account.

The FirstIgnite settings live at Setup → System Settings → Third Party Services → FirstIgnite.

The Minuet Setup ribbon, with System Settings as the first item

The System Settings navigation with Third Party Services expanded. FirstIgnite is the last entry in the list

If your administrator can't see that option, it's hidden for their security group, and a fully up-to-date Minuet will still hide it. In the Minuet Admin Console: Setup → Security Groups → select the group → expand Setup → System Settings → API → enable FirstIgnite Auto Connect.

The Admin Console is a separate application, not a page in the Minuet web app. Don't look for it in the browser. Institutions usually run it as a published remote application, so it opens like an ordinary program on the administrator's desktop. If they don't have it, Inteum support can set them up.

If your administrator can't find System Settings at all, they don't have Minuet administrator rights. If the FirstIgnite option still doesn't appear after enabling the security-group setting, your Minuet licence may not include API access. Inteum support can confirm.

The connector asks for one, so it's worth knowing what you're picking.

An Endpoint Access Group is a named list of the API endpoints a client is allowed to call. Every API client in Minuet has exactly one, and it is the first of the two gates on every request: the group decides which calls FirstIgnite may make, and the Minuet user the client runs as decides which records those calls return. Both are yours, and the second is the one that catches people out. See Minuet API endpoints required by FirstIgnite.

Your Minuet administrator owns it. Nobody at FirstIgnite can see or change it. It lives in Minuet at Setup → System Settings → Advanced → API, under Endpoint Access Groups, and it can be edited at any time after setup, including from the pencil beside the picker on the FirstIgnite screen.

The Select an Endpoint Access Group field on the FirstIgnite setup screen, with the pencil that opens it for editing

On the guided path, Minuet creates the group for you and names it FirstIgnite Auto Connection Group. Opening it shows FirstIgnite's endpoints grouped by the Minuet record each one touches, with a short note on what it powers, and an Enable all required endpoints button. Everything else in Minuet's API sits under Other endpoints and stays unticked, because FirstIgnite doesn't ask for it.

The Endpoint Access Group editor, listing FirstIgnite's required endpoints with a tick and a description each, and an Other endpoints section left unselected

The number of endpoints changes over time, so don't be alarmed if what your instance shows doesn't match a count you've read somewhere. It grows as FirstIgnite ships features, and it occasionally shrinks when Inteum makes an endpoint always available and drops it from the list. When a feature starts reporting missing permissions on a connection that used to work, that's the set having moved. Refresh Required Endpoints, on the FirstIgnite screen in Minuet, brings the group up to date in one click without reconnecting.

Narrowing the group removes specific capabilities. Removing it altogether, or revoking the client, ends FirstIgnite's access when its current token expires. See Controlling what FirstIgnite can see.

Your Minuet administrator starts the connection from the FirstIgnite setup screen in Minuet and chooses whether to connect to FirstIgnite's US or EU environment. Minuet grants the API access FirstIgnite needs; there is no endpoint list to work through by hand.

On Minuet 20 or later, connect from Minuet, not from FirstIgnite. Start the connection at Setup → System Settings → Third Party Services → FirstIgnite → Connect to FirstIgnite. A team admin on the FirstIgnite account then needs to click Confirm Connection within 15 minutes.

The setup wizard you may see under Minuet Settings in FirstIgnite is the older, credential-based method. It's only for Minuet instances older than version 20, and it needs at least Minuet 19. Don't use it on Minuet 20 or later.

The FirstIgnite setup screen in Minuet: choose US or EU, pick the Minuet user the integration runs as, pick the Endpoint Access Group, then click Connect to FirstIgnite

Minuet then produces a link. Someone who is a FirstIgnite team admin has to open that link while signed in to FirstIgnite, review the institution, server address and FirstIgnite team shown, and click Confirm Connection.

The Confirm Connection page in FirstIgnite, showing the institution, server address and FirstIgnite team before the link is made

To reconnect or change credentials later, run Connect to FirstIgnite again from Minuet. It updates the existing connection and tests the new credentials first. If a connection is already active, confirming a new one with bad credentials will not break it. The existing connection stays until a new one verifies.

The connection card under Minuet Settings in FirstIgnite shows your Minuet URL and the first characters of the Client ID. Test Connection re-runs the check at any time. A clean result reads All required API permissions verified.

The Minuet Connection card in FirstIgnite settings after a passing test, reading Connected and All required API permissions verified

Connecting establishes access. It does not switch any feature on.

A FirstIgnite team owner or admin turns individual capabilities on in FirstIgnite, under Minuet Settings, in the Operations section: reading CRM data, logging emails, creating marketing targets, sending companies and contacts, syncing enrichment, and syncing AI summaries. See What each Minuet feature needs, and who can turn it on.

One to be careful with. Sync AI Summaries writes over whatever is in the destination field, with no prompt, every time a summary finishes. It is off by default and the manual sync asks first. See Syncing FirstIgnite summaries to Minuet safely.

This section is for your network team.

If Minuet is hosted by Inteum at yourorg.inteum.com, there is nothing to do here.

If you run Minuet yourselves, expect to allowlist FirstIgnite. Every self-hosted customer so far has needed it, and it has been the only thing their IT team had to do.

You can test the path before involving FirstIgnite at all, with no credentials. From outside your network, request this path on your Minuet host:

/<minuet-path>/MinuetIdentity/idsrv/.well-known/openid-configuration

A 200 means the path is open. A connection that drops instantly means the traffic isn't reaching Minuet. That is an edge routing or allowlist problem, not a credentials problem.

FirstIgnite runs separate US and European environments. Use the one your institution is set up on; signing in on the wrong one redirects you.

Your Minuet administrator can revoke the API client or remove its Endpoint Access Group at any time. FirstIgnite loses access when its current access token expires. Your Minuet instance sets that lifetime, and on a default configuration it is short. Nothing on our side has to happen first.

From FirstIgnite, a team owner or admin can switch individual operations off, or delete the integration entirely. Deleting removes the connection and its settings for your team; you can reconnect later.

If something isn't working, see Troubleshooting the Minuet integration.