Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Persistent Access Tokens are tentatively scheduled be deployed in early December with CloudCard Release 22.10.27.

API Authentication

The CloudCard API now supports Persistent Access Tokens (refresh tokens). Persistent Access Tokens are only used to request Authentication Tokens (session tokens), which can be used by service accounts to make API requests. Authentication Tokens expire automatically after 12 hours but can be deleted earlier by logging out.

API Authentication Flow

  1. A Persistent Access Token is created for a service account by a CloudCard director in the user interface. Get a Persistent Access Token.

  2. Next, the Persistent Access Token is used to Get an Authentication Token (Session Token).

  3. To use an Authentication Token, it should be passed as the value in the X-Auth-Token header for authenticated API requests.

  4. When finished with an Authentication Token, it should be deleted. Log Out Authentication Token(s).

Username and Password Authentication

This authentication strategy is designed to be used with user interfaces and is not the recommended authentication method for API Integrations.

Login:

URI: https://api.onlinephotosubmission.com/api/login

HTTP Method: POST

Example HTTP Request Body
{
	"username":"myUserName",
	"password":"myPassword"
}
Example Response
200 OK
{
    "username": "myUserName",
    "roles": [
        "ROLE_CARDHOLDER",
        "ROLE_DIRECTOR",
        "ROLE_OFFICE"
    ],
    "access_token": "lotsOfRandomNumbersAndLetters"
}
  • No labels