Getting started
This guide covers everything you need to begin integrating with our APIs: signing in, exploring the catalog, getting access, and making your first call.
Account creation
This portal uses single sign-on (SSO). Sign in with your SCOR or partner organization credentials — there's no separate account or password to manage.
- Select Sign in and authenticate with your organization credentials.
- On first sign-in, your access level is assigned automatically based on your organization identity.
Explore the API catalog
Take a moment to understand what's available and how it's organized before requesting access.
- Browse the catalog — every published API is listed on the APIs page, with its purpose, capabilities, and available endpoints.
- Pick the right version — an API can have multiple versions, listed in its own left-hand menu. Older versions may be marked deprecated - prefer the most recent one unless you have a specific reason not to.
- Read the reference — each API page includes its full OpenAPI reference (endpoints, request/response schemas, examples).
- Try it, right here — every API page has a built-in "Try it" panel to send real test requests directly from the portal, with your own credentials, no separate tool required.
- Generate a client — download the OpenAPI document (YAML/JSON) from the API's page to generate a client in your language of choice, e.g. with openapi-generator.
Navigating environments
Purpose-built environments support every phase of your integration.
| Name | Description | How to get access | Base URL |
|---|---|---|---|
| Sandbox | Mock environment for testing, no sensitive data | Available immediately after sign-up, no approval required | https://api-sandbox.scor.com |
| UAT | User Acceptance Testing, for validating integrations before go-live | Request access via your application page | https://api-uat.scor.com |
| Production | Live environment for real data and transactions | Request access via your application page, subject to approval | https://api.scor.com |
Each environment supports a specific stage of development, from first exploration to a fully tested, production-ready integration.
Getting access
Every API's authentication requirement is shown on its own documentation page - it is generated directly from that API's live Kong Gateway configuration, so it always matches what is actually deployed, never a hand-maintained description. Two requirements exist today, depending on the API:
- OIDC Bearer token - the API requires a signed-in identity token, scoped to specific Azure AD groups (listed on the API's page under "Authentication"). Request membership of the required group from the API's owning team; once granted, obtain a token through your organization's SSO and send it as a Bearer token.
- API key - the API is protected by a simple key. Requesting one typically goes through an Azure AD application registration (via SNOW) - contact the API's owning team if you're unsure of the exact process for a given API.
If you run into any issues, each API's owning team is your first point of contact - listed on that API's own page. For anything else, reach the platform team via SAIL Microsoft Teams.
2. Find your API
Check its "Authentication" section.
3. Request access
AAD group or API key, from the owning team.
4. Call the API
With your Bearer token or API key.
See Navigating environments above for what each environment is for and its base URL.
Make your first call
Replace the header below with whichever the API's own page requires -
Authorization: Bearer <token> for OIDC-protected APIs, apikey: <key> for API-key-protected ones:
curl -i https://api-sandbox.scor.com/v1/example \
-H "Authorization: Bearer YOUR_TOKEN"
Prefer not to leave the portal? Use the Try it panel directly on the API's own reference page to send this same request interactively, with your credentials already filled in.
Browse APIs