Sign inGet started
Docs
Get started

Sage Intacct API Authentication

How to authenticate Sage Intacct API requests: one Bearer API key plus a connectionId. MindCloud handles Sage Intacct's custom auth scheme for you.

Every Sage Intacct API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Sage Intacct account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.

Steps to authenticate

  1. Create a MindCloud account at app.mindcloud.co if you do not already have one.
  2. Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
  3. Create a Sage Intacct connection in Connections. Sage Intacct uses its own authentication scheme. You provide whatever it requires when you create the connection — MindCloud handles the provider-specific details for you.
  4. Copy the connection’s connectionId — you will send it on every request alongside your MindCloud API Key.

How requests are authenticated

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Sage Intacct account that should run the action. MindCloud stores and refreshes the Sage Intacct credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions.

For example, calling Check GLBATCH Duplicate with an Sage Intacct connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/intacct/actions/check-glbatch-duplicate/run" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "arguments": {}
}'

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which Sage Intacct account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect Sage Intacct

Ask a Sage Intacct company administrator to complete the setup below. You need an active Web ServicesSage Intacct’s feature that lets other applications exchange information with your company. developer license, a Sender IDThe identifier Sage issues with a developer license, paired with its own password. and password, and a Web Services userA dedicated account that lets an integration access company data without signing in to the Sage Intacct interface. for the company you want to connect.

  1. Get your sender credentials

    If you do not already have a Web ServicesSage Intacct’s feature that lets other applications exchange information with your company. Sender IDThe identifier Sage issues with a developer license, paired with its own password. and password, request them from your Sage Intacct account representative. In the connection form, enter the sender password in Sender Password and the Sender IDThe identifier Sage issues with a developer license, paired with its own password. in Sender IDThe identifier Sage issues with a developer license, paired with its own password.. Preserve capitalization; both values are case-sensitive.

  2. Enable Web ServicesSage Intacct’s feature that lets other applications exchange information with your company. for your company

    Sign in to the company as an administrator. Open Subscriptions and enable Web ServicesSage Intacct’s feature that lets other applications exchange information with your company. if it is not already enabled.

    Company → Admin → Subscriptions

  3. Authorize your Sender IDThe identifier Sage issues with a developer license, paired with its own password.

    Open the Security tab and select Edit. In Web ServicesSage Intacct’s feature that lets other applications exchange information with your company. authorizations, select Add, enter the same Sender IDThe identifier Sage issues with a developer license, paired with its own password. used in Sender IDThe identifier Sage issues with a developer license, paired with its own password., set its status to Active, and save.

    Company → Setup → Configuration → Company → Security

  4. Create a dedicated Web Services userA dedicated account that lets an integration access company data without signing in to the Sage Intacct interface.

    Select Add next to Web ServicesSage Intacct’s feature that lets other applications exchange information with your company. users. Enter a unique User ID, a Username and an Account email address you can access; complete the contact details and choose the appropriate User type. Leave Admin privileges Off unless the integration needs them. Save, select Create, and verify with your administrator password. Give this user only the permissions needed for the work you want the connection to perform.

    Company → Admin → Users, roles, and groups → Web Services users

  5. Enter the company and user credentials

    Return to the connection form. Enter the company ID used to sign in to the target Sage Intacct company in Company Id. Enter the dedicated Web Services userA dedicated account that lets an integration access company data without signing in to the Sage Intacct interface. ID in User Id and that account’s password in User Password. Use the User ID rather than the Username or email address. Your administrator can reset a Web Services userA dedicated account that lets an integration access company data without signing in to the Sage Intacct interface.’s password if necessary; resetting a password also requires updating any other integration that uses that account.

  6. Check all five fields

    Confirm Company Id, User Id and User Password belong to the same company and Web Services userA dedicated account that lets an integration access company data without signing in to the Sage Intacct interface.. Confirm Sender IDThe identifier Sage issues with a developer license, paired with its own password. and Sender Password are the sender credentials authorized for that company. Then submit the connection form.

Keep your key safe

Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.