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.
In Acumatica, go to Integration → External Applications
Create a new record, set Type to OAuth 2.0, name it "On Belay"
Set Client ID to anything memorable (e.g. "onbelay-integration")
Copy the Client Secret that Acumatica generates
Click "View Redirect URI" and confirm it shows https://app.onbelay.ai/api/oauth-callback/acumatica
Save the record, then click "Connect with OAuth" below
Ready to connect?
Go directly to the integrations page in your dashboard.
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 |
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.
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.
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 →