Authentication

You'll need to authenticate your requests to access most of the endpoints in the eeds API. In this guide, we'll look at how authentication works. The eeds API supports two authentication workflows. Which to use depends on whether you're accessing the API as an individual user or as an organization.

User credentials flow

To authenticate using your eeds user account, make a POST request to https://newapi.eeds.com/api/api/token providing your username and password as JSON:

curl -X "POST" \
  --url "https://newapi.eeds.com/api/token" \
  -H 'Content-Type: application/json' \
  -d $'{
    "username": "eeds-username",
    "password": "eeds-password
  }'

If successfully authenticated, you will receive a response that includes an access token.

{
  "username": "eeds-username",
  "token": "V1ROclFTMTRiVWhwTWw4M2FVNWFkVGQyTldNNk1UcGphUTotU"
}

The access token should be attached to subsequent requests to the API in the Authorization header.

curl -G https://newapi.eeds.com/api/conferences \
  -H "Authorization: Bearer V1ROclFTMTRiVWhwTWw4M2FVNWFkVGQyTldNNk1UcGphUTotU"

Client credentials flow

You may also authenticate with the eeds API using the client credentials flow. Rather than authenticating as a specific user, you will authenticate using your organization's API key. When establishing a connection using client credentials, you will need your client ID and client secret, which were provided when you requested access to the API.

To retrieve an access token, make a GET request and provide the required client_id, client_secret, and grant_type parameters along with a Content-Type header that has the value application/x-www-form-urlencoded.

curl -X "GET" \
  --url "https://newapi.eeds.com/api/client/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  --data-urlencode "client_id=123456" \
  --data-urlencode "client_secret=0SgUrX5nffDHlOKyrOfb" \
  --data-urlencode "grant_type=client_credentials"

Always keep your client secret safe and contact eeds to reset it if you suspect it has been compromised.

If successfully authenticated, you will receive a response that includes an access token.

{
  "token_type": "Bearer",
  "expires_in": 3600,
  "access_token": "V1ROclFTMTRiVWhwTWw4M2FVNWFkVGQyTldNNk1UcGphUTotU"
}

The access token should be attached to subsequent requests to the API in the Authorization header.

curl -G https://newapi.eeds.com/api/conferences \
  -H "Authorization: Bearer V1ROclFTMTRiVWhwTWw4M2FVNWFkVGQyTldNNk1UcGphUTotU"