Authorization
Quip
Prerequisites
Before creating a Quip credential, you need to obtain your Personal Access Token from your Quip account. Quip uses Personal Access Token authentication for all API requests, with the token sent in the Authorization header with the Bearer prefix.
To obtain your Quip Personal Access Token, follow these steps:
-
Sign in to your Quip account using your administrator credentials.
-
Navigate to your account settings or profile settings in the Quip interface.
-
Look for the API or Personal Access Tokens section in your account settings, or navigate to Settings > API or Developer > Personal Access Tokens.
-
If you don't have a Personal Access Token yet, look for the option to generate or create your Personal Access Token.
-
Click Generate Personal Access Token or Create Personal Access Token to create a new token.
-
Configure your Personal Access Token settings:
- Enter a name for the token (e.g., "Nexla Integration")
- Review and select the permissions or scopes for the token (if applicable)
-
Click Generate or Create to create the Personal Access Token.
-
Copy the Personal Access Token immediately after it's generated, as it may not be accessible again after you navigate away from the page.
-
Store the Personal Access Token securely, as you will need it to configure your Nexla credential. The Personal Access Token is sensitive information and should be kept confidential.
The Personal Access Token is sent in the Authorization: Bearer {token} header for all API requests to the Quip API. The Personal Access Token authenticates your requests and grants access to Quip resources based on your account permissions. If your Personal Access Token is compromised, you should immediately revoke it in your Quip account settings and generate a new one. For detailed information about obtaining Personal Access Tokens, API authentication, and available endpoints, refer to the Quip API documentation.
Create a Quip Credential
- To create a new Quip credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Quip

Credential Name & Description
-
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 provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.
Personal Access Token Authentication
Quip uses Personal Access Token authentication for all API requests. The Personal Access Token is sent in the Authorization header with the Bearer prefix to authenticate API requests to the Quip API.
-
Select the authentication method from the Quip API Authentication Method pulldown menu. Available options include Personal Authentication (default). The authentication method determines how your Quip account will be authenticated.
-
Enter your Quip Personal Access Token in the Personal Access Token field. This is the Personal Access Token you obtained from your Quip account settings (Settings > API or Developer > Personal Access Tokens). The Personal Access Token is sent in the
Authorization: Bearer {token}header for all API requests to the Quip API. The Personal Access Token is sensitive information and must be kept confidential.Your Quip Personal Access Token can be found in your Quip account settings under Settings > API or Developer > Personal Access Tokens. The Personal Access Token is sent in the
Authorization: Bearer {token}header for all API requests to the Quip API.If your Personal Access Token is compromised, you should immediately revoke it in your Quip account settings and generate a new one. The Personal Access Token provides access to your Quip account data and should be treated as sensitive information. Keep your Personal Access Token secure and do not share it publicly.
For detailed information about obtaining Personal Access Tokens, API authentication, and available endpoints, see the Quip API documentation.
Save the Credential
-
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.
-
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.