Using OAuth 2.0 to Access EtMDB API Endpoints

EtMDB API use the OAuth 2.0 standard for authentication and authorization. EtMDB supports common OAuth 2.0 scenarios such as those for web server, installed, and client-side applications.

Application management views

  • Register Application
  • Create a new application or get the list of applications

  • Replace $APPLICATION-ID on the URL
  • Application details: "$APPLICATION-ID/"
  • Update Application: "$APPLICATION-ID/update/"
  • Delete Application: "$APPLICATION-ID/delete/"
  • Token management views
    Access token URL

    curl -X $HTTP_METHOD ""

    Get the list of authorized access token and you can revoke them

    curl -X $HTTP_METHOD ""

    Delete Authorizated access token with ID

    curl -X $HTTP_METHOD "$ACCESS-TOKEN-ID/delete/"

    Access token and refresh token with one to these two methods below

    curl -X $HTTP_METHOD -d "grant_type=password&username=$USERNAME&password=$PASSWORD&scope=$SCOPE" -u "$CLIENT-ID:$CLIENT-SECRET-KEY" ""

    curl -X $HTTP_METHOD -d "grant_type=password&username=$USERNAME&password=$PASSWORD&scope=$SCOPE" -u "https://$CLIENT-ID:$"

    Sucessful return result when getting access and refresh token
    {"refresh_token": "$REFRESH-TOKEN", "token_type": "$TOKEN-TYPE", "expires_in": 36000, "scope": "$SCOPE", "access_token": "$ACCESS-TOKEN"}

    Check grand type
    {"error": "unsupported_grant_type"}

    Client id or secret incorrect
    {"error": "unauthorized_client"}

    Client not valid
    {"error": "invalid_client"}

    Scope incorrect
    {"error": "invalid_scope"}

    Password or username incorrect
    {"error_description": "Invalid credentials given.", "error": "invalid_grant"}

    Last update on:Nov. 14, 2017, 9:36 EtMDB API Developers