ProShop Integration

Connecting ProShop ERP lets a team search, analyze, and build applications and automations on its parts, work orders, and production data. Setup takes three steps: create an API authorization in ProShop, gather the connection details, and share them with Complement securely.

How It Works

Complement connects to the ProShop instance from its hosted platform through ProShop’s GraphQL API over HTTPS. When ProShop hosts the instance, nothing is installed on site and no inbound firewall rules are needed. For on-premises instances, Complement sets up network access with the IT team.

The first sync backfills history. After that, Complement pulls changes on a schedule, so applications and agents always work from current data.

Synced data stays inside Complement’s permission model. Administrators choose which people and applications can see each data source.

The entire Complement platform is ITAR compliant. Only US persons operate the platform, all data is encrypted in transit and at rest, and customers with ITAR-controlled data run in AWS GovCloud.

Requirements

• ProShop 5.2.3 or later, which added the client credentials flow Complement uses.
• An active ProShop API. If API access was turned off on the instance, ask ProShop support to turn it back on.
• A ProShop system administrator to create the API authorization in Step 1.

Setup

Step 1: Create a ProShop API Authorization

A ProShop system administrator creates an OAuth 2.0 authorization for Complement. In ProShop, open System Config, then Configuration Links, then Manage Authorizations, and add an authorization:

• Name: Complement
• Maximum Scope: the modules to share, each with read access and separated by spaces, such as parts:r workorders:r purchaseorders:r. Scope names are lowercase.
• Direct Login and Active checked, so Complement can authenticate with the client credentials flow

The more modules the authorization includes, the more Complement can do across the shop. To share ITAR jobs or parts, add itarokay:o, or records flagged ITAR stay hidden from the API.

Save the authorization and record its Unique ID and Shared Secret for Step 3.

Step 2: Gather Connection Details

Value	Description	Example
Instance URL	The base HTTPS URL used to sign in to ProShop	https://yourcompany.adionsystems.com
Client ID	The authorization’s Unique ID from Step 1	XXXX-XXXX-XXXX
Client secret	The authorization’s Shared Secret from Step 1	••••••••

Step 3: Share the Details with Complement

Send the values from Steps 1 and 2 to your Complement contact through a secure channel, such as a one-time secure link from Complement or the company’s secure file sharing.

Write Access

Complement starts read-only. To let applications write back to ProShop, such as updating a work order, change that module’s scope from :r to :rw in the authorization’s Maximum Scope. For example, workorders:rw allows work order updates. Grant write access only for specific approved workflows.

Troubleshooting

Issue	Possible Cause	Solution
Complement cannot authenticate	The client ID or secret is wrong, or the authorization is not marked Active	Check the authorization in Manage Authorizations and share the credentials again if they changed
The connection is refused or times out	The ProShop API is not active on the instance, or a firewall blocks Complement	Ask ProShop support to activate the API. For on-premises instances, contact Complement to set up network access
Some data is missing	The authorization’s Maximum Scope leaves out the module	Add the module with read access, such as purchaseorders:r
ITAR jobs or parts are missing	The Maximum Scope leaves out itarokay:o	Add itarokay:o to the authorization