Acumatica

OAuthERPOrg connection

Org-level connection

Acumatica is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.

How to connect

Enter your Acumatica instance URL in the field above (e.g. https://mycompany.acumatica.com)

In Acumatica, go to Integration → Connected Applications (screen SM303010) → Add

Set Flow Type to "Authorization Code", add On Belay's redirect URI, and save

Copy the generated Client ID and create a Client Secret under the Secrets section

Paste the Client ID and Client Secret below, then click "Connect with OAuth"

Ready to connect?

Permissions (scopes)

These are the data scopes On Belay can be granted for Acumatica. Your org admin controls which scopes are enabled per group.

Scope	Description	Access
`api`	Full Acumatica REST API access	Read / Write
`offline_access`	Refresh token (offline access)	Read only

Troubleshooting

"redirect_uri_mismatch" error during OAuth

Your OAuth app's authorized redirect URIs don't include the On Belay callback URL. Add https://app.onbelay.ai/api/oauth-callback/acumatica to the allowed redirect URIs in your OAuth app settings.

"invalid_scope" error

The API or scope isn't enabled in your cloud project. For Google integrations, make sure the relevant API (e.g. Google Ads API, Search Console API) is enabled in Google Cloud Console for your project.

Connected but Claude can't access data

Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.

Still stuck? We're happy to help.

Contact support →