Getting Started

Welcome to the Solar API Portal! This guide will help you get up and running quickly with our APIs.

Step 1 - Request API credentials

Solar relies on OAuth 2.0 (Open Authorization), a secure and industry-standard protocol, to grant third-party applications access to Solar resources. By using OAuth, Solar ensures secure and controlled access to our APIs, providing a reliable and trusted method for authentication.

To obtain Client ID and Client Secret, follow these steps :

  • Register: Use registration form to request access to Solar API.

  • Receive login information: Our integration team will process your access request. When your request is approved, we'll send you an email with all the details and instructions to your inbox. Follow the instruction in the email to get a Client ID and Client Secret.

Step 2 - Configure OAuth 2.0

If you have an OAuth 2.0 enabled application, use following details:

  • Grant Type: Client Credentials

  • Access Token URL: Use the following endpoint to obtain access token:
    https://sgidp.b2clogin.com/sgidp.onmicrosoft.com/b2c_1a_client_credentials/oauth2/v2.0/token

  • Client ID and Client Secret: Use details provided by Solar.

  • Client Authentication: Send client credentials in body.

  • Scope: https://sgidp.onmicrosoft.com/api.procurement/.default

If you do not have an OAuth 2.0 enabled application and you want to do the client credentials flow manually, here is a HTTP example :

Also here is a .Net example for the client credentials flow:

Step 3 - Explore the API Documentation

Familiarize yourself with the API endpoints and their functionalities:

  • API Reference: Detailed documentation on each endpoint, including request and response formats.

  • Example Requests: Sample code snippets to help you understand how to make API calls.

Step 4 - Making API Requests

Once you have obtained an access token, you can make authenticated API requests:

  • Include Access Token in Requests: Add the access token to the Authorization header of your API requests using the Bearer schema.

  • Token Expiry : Access tokens have a limited lifespan of 60 minutes.