Authorization
Expensify API
Prerequisites
Before creating an Expensify API credential in Nexla, you must obtain partner credentials from the Expensify Integration Server. Expensify uses a partnerUserID and partnerUserSecret pair to authenticate all API requests.
Obtain Expensify Partner Credentials
Expensify partner credentials are generated directly from a dedicated tools page within your Expensify account. Follow the steps below to obtain them.
-
Sign in to your Expensify account at expensify.com.
-
Navigate to www.expensify.com/tools/integrations/ — this page is the dedicated credential generation tool for Expensify's Integration Server.
-
On the integrations page, your partnerUserID and partnerUserSecret are displayed. These credentials are generated specifically for API and integration access.
Copy and store both the partnerUserID and partnerUserSecret in a secure location immediately. The partnerUserSecret will not be shown again after you navigate away from the page. Treat these credentials like a password — never share your partnerUserSecret.
- Record both values for use in the Nexla credential configuration below.
API Access and Network Requirements
Before proceeding, verify the following:
-
Active Expensify account: An active Expensify account is required to access the Integration Server.
-
Administrator access: Generating partner credentials requires that you have administrator-level access to your Expensify account.
-
Network connectivity: Ensure your network environment allows outbound HTTPS connections to
https://integrations.expensify.com, which is the Expensify Integration Server endpoint used by all API calls.
All Expensify API requests are made via HTTPS POST to https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations. Nexla uses this endpoint for all data source and destination operations with your Expensify account. For additional information about the Expensify API, refer to the Expensify API Reference.
Create an Expensify API Credential
- To create a new Expensify API credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
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 to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.
Expensify Integration Server Configuration
- Enter the Expensify Integration Server URL in the Expensify Integration Server URL field. The standard production endpoint is
https://integrations.expensify.com. Use this default value unless your organization has been instructed to use an alternative server URL.
The Integration Server URL defaults to https://integrations.expensify.com for all standard Expensify accounts. This is the base URL for the Expensify Integration Server — Nexla appends the required API path automatically when making requests.
Partner Credentials Configuration
-
Enter your Expensify partner user ID in the Expensify partnerUserID field. This is the unique identifier generated on the Expensify integrations page and is used to identify your integration when making API requests.
-
Enter your Expensify partner user secret in the Expensify partnerUserSecret field. This confidential key is paired with the partner user ID to authenticate all API requests sent to the Expensify Integration Server.
The partnerUserID and partnerUserSecret are sensitive credentials and should be kept secure. Nexla stores these credentials securely and uses them only to authenticate API requests to the Expensify Integration Server on your behalf.
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.