Skip to main content

Gigapipe docs

Authentication

The Gigapipe Client uses API keys to authenticate requests. You can view and manage your API keys on the Gigapipe Dashboard.

The secret key has the prefix gigapipe_sk whereas the public one starts with gigapipe_pk. When used together, they provide users with the authentication token they need to make requests against the API or use the Gigapipe Client SDK. Alternatively, users can use their email and password to get the authorization authentication .

Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.

Authentication to the API is performed via HTTP Basic Auth. Provide your API key as the basic auth value.

Create your API Client SDK

The Gigapipe Client should be created on the Gigapipe Dashboard. When adding a new app, two things will happen:

  1. The organization will get a Client ID in case it does not have one yet.
  2. The user will get a Secret key.

As it can easily be noticed, all the users inside the organization will share the Client ID, whilst the Secret key is individual for each user.

Get the authorization token

Obtain the authorization token that will allow you to make requests to the API

curl -X 'GET' \
'https://api.gigapipe.com/v1/sdk/authorize' \
-H 'accept: application/json' \
-H 'client-id: <your_client_id>' \
-H 'client-secret: <your_client_secret>'
  # Payload response
{
"access_token": "your_access_token",
"refresh_token": "your_refresh_token"
}

Use the access token to make calls against the API