OAuth and environments
ScanSource uses OAuth 2.0 client credentials for application access, plus a subscription key on the API gateway.
Production and platform runtime: organization Client ID and Client Secret → access token. Do not use a personal developer Try It key as the production identity.
Start here · Sign in · Account & sign-in help · Popular platforms
Warning: organization credentials vs Try it keys
After Active, open Profile → Organization Subscription Information for organization Client ID, Client Secret, and organization subscription key.
Portal Primary and Secondary subscription keys (shown with APIs / Try it) are for portal testing only — not for platforms or production.
How authentication works
Client credentials grant
Your application exchanges organization Client ID and Client Secret for an access token, then calls APIs with that token.
Subscription key
Required by the API gateway. Production apps use the organization subscription key from Organization Subscription Information, not a personal Try it key.
Portal Try it
After sign-in, interactive testing in the developer portal may use portal subscription keys. Prefer DEV/TEST portals for day-to-day integration work.
Environments
Use TEST portal and test OAuth/API hosts for integration work. Use production hosts only with production app credentials.
Do not mix environments
Do not point a production platform connector at test credentials, and do not use production secrets in a throwaway sandbox script.
Sandbox vs production
Configure platforms against TEST credentials and hosts first; promote to production credentials only when ready.
Where to find credentials
Profile → Organization Subscription Information (after Active).
Platform connectors vs custom APIs
Path A — platforms
Paste organization credentials into the vendor tool (for example QuoteWerks). You usually do not hand-build OAuth token requests.
Path B — Partner Direct
Your middleware obtains tokens with client credentials and calls entitled APIs. Specs and Try It open after approval and product assignment.
Frequently asked questions
Can I use Try it keys in production?
No. Use organization Client ID, Client Secret, and organization subscription key from Profile → Organization Subscription Information after Active.
How do I get a token?
With the client credentials grant against the token endpoint for your environment (TEST vs production). Exact hosts and scopes appear in entitled API documentation after Active.
Why both token and subscription key?
The API Management gateway enforces a subscription key in addition to the bearer token for most products.
Platform connector — do I build OAuth?
You still need organization credentials after Active. OAuth token plumbing is usually inside the vendor connector.
Why can’t I see credentials or APIs?
Your account is not Active, or products are not assigned. Submitted means review is in progress.
Ready to continue?
Sign in · Start here · Account & sign-in help · Popular platforms