Acumatica Configuration

The superglue agent can read and write Acumatica records, and it can change setup data that the standard Acumatica API does not cover. This includes payment terms, numbering sequences, enabled features, module preferences, users, roles, and branch access. This guide walks you through the one-time setup, which takes about ten minutes.

!

Setup changes apply to the whole company, and some cannot be undone. Try them on a test tenant first.

What to expect

• One endpoint for setup data. The first time the agent changes setup data, it adds a web service endpoint named Superglue to your instance. The endpoint stores screen mappings only and contains no code. Adding or changing it does not restart the site or sign anyone out.
• Approval first. The agent asks for your approval before it adds the endpoint and before each change to your data.
• Runs as the API user. All calls run as the Acumatica user that signs in. The agent can only see and change what that user’s roles allow.

Setup

1. Create an API user in Acumatica

   1. Open Users (SM201010) and create a user for superglue, for example superglue-api.
   2. On the Roles tab, select the roles for the areas the agent works in. To let the agent change setup data, also select Customizer.
   3. Select the branch access role of every branch the agent needs. Open Branches (CS102000) to see the Access Role of each branch. Without it, lists such as customers, orders, and warehouses come back empty, with no error.
   4. For time, expense, and service features, link the user to an employee record.

2. Create a connected application in Acumatica

   1. Open Connected Applications (SM303010) and add an application, for example “superglue”.
   2. Set OAuth 2.0 Flow to Authorization Code.
   3. On the Secrets tab, add a shared secret and copy its value. Acumatica shows the value only once. Without a secret, the sign-in fails with unauthorized_client.
   4. On the Redirect URIs tab, add https://app.superglue.cloud/api/auth/callback.
   5. Save. Copy the Client ID. It has the form <GUID>@<tenant>.

3. Connect Acumatica in superglue

   1. Create an Acumatica system in superglue with your site URL, for example https://client.acumatica.com or https://erp.example.com/AcumaticaERP.
   2. Enter the client ID and the client secret, then start the OAuth sign-in.
   3. In the Acumatica sign-in window, sign in as the API user and approve access.

   The site must use a trusted HTTPS certificate. A self-signed certificate is not supported.

4. Test the setup in superglue

   1. Tell the agent: “List five vendors from Acumatica.” If you get a list back, the connection works.
   2. Tell the agent: “Show me the payment terms in Acumatica.” The first time, the agent asks to add the Superglue endpoint. Approve it. If you get the payment terms back, setup changes work too.

Limits

• Concurrent API users. Your Acumatica license limits how many API sessions can run at the same time. The agent runs requests one at a time to stay within the limit.
• Features and license. Some features need a license. Check with your Acumatica partner before you ask the agent to turn on a feature.
• Passwords. The agent can create users and change their roles, but it cannot copy passwords from another system. New users set their own password.

Without a connected application

If you cannot create a connected application, superglue can sign in with the API user’s username and password instead. Each tool then logs in at the start and logs out at the end of its run.

Remove access

To remove access right away, delete the connected application in Connected Applications (SM303010) or disable the API user in Users (SM201010). To remove the Superglue endpoint, delete it in Web Service Endpoints (SM207060).