Skip to main content

Authorization

Follow this guide to create a new Anaplan credential that will allow Nexla to authenticate to and exchange data with your Anaplan account.
anaplan_api_auth.png

Anaplan

Prerequisites​

Before creating an Anaplan credential, you'll need to obtain a JWT access token from the Anaplan authentication API. The Anaplan API uses Bearer token authentication with JWT access tokens obtained through Base64-encoded credential authentication.

Anaplan Account Setup​

To obtain the required access token for Anaplan:

  1. Sign in to Anaplan: Navigate to https://anaplan.com/ and sign in to your Anaplan account. If you don't have an account, you'll need to contact Anaplan to set up an account.

  2. Obtain Credentials: You'll need your Anaplan username and password. These are the same credentials you use to sign in to the Anaplan web application.

  3. Generate Access Token: The Anaplan API requires a JWT access token for authentication. To obtain this token:

    • Make a POST request to https://auth.anaplan.com/token/authenticate
    • Include your Anaplan username and password encoded in Base64 format in the Authorization header
    • The format should be: Authorization: Basic {base64(username:password)}
    • The API will return a JWT access token in the response

  4. Extract Access Token: From the authentication response, extract the JWT access token. This token will be used for all subsequent API requests to Anaplan.

Anaplan access tokens are JWT tokens that authenticate API requests. The tokens are obtained by authenticating with Base64-encoded credentials. Access tokens may expire, so you may need to refresh them periodically. For complete information about Anaplan API authentication, see the Anaplan API Documentation.

API Access Requirements​

Anaplan API access requires:

  • Valid Anaplan Account: You must have an active Anaplan account with appropriate permissions
  • JWT Access Token: A token obtained from the Anaplan authentication API
  • Workspace Access: The access token must have permissions to access the workspaces and models you want to interact with

The Anaplan API uses Bearer token authentication, where the JWT access token is sent in the Authorization header with the format Bearer {token}. All API requests must use HTTPS.

For complete information about Anaplan API authentication and getting started, see the Anaplan API Documentation.

Create an Anaplan Credential​

  • To create a new Anaplan credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Anaplan

AnaplanCred.png

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They should be used to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Access Token Configuration​

  1. Anaplan JWT Access Token: Enter your Anaplan JWT access token in the Anaplan JWT Access Token field. This is the token obtained from the Anaplan authentication API (https://auth.anaplan.com/token/authenticate). The token is used in the Authorization header as Bearer {token} for all API requests.

The JWT access token is sensitive information that should be kept secure. Nexla will store this credential securely and use it only for API authentication purposes. The token is sent in the Authorization header as Bearer {token} for all Anaplan API requests. If your token expires, you'll need to obtain a new token and update the credential.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.