API Connection Setup
This page explains how to connect Business Central to the Certify API. These fields are in the Certify Connection Setup group on the Certify Setup card.
Connection Fields
| Field | Description |
|---|---|
| Base URL | The root address of the Certify API. Defaults to https://api.certify.com/v1/. |
| API Key | The API key issued for your Certify account. Sent as the x-api-key header. |
| API Secret | The API secret for your account. Sent as the x-api-secret header. Shown masked. |
| Use Debug Mode | When enabled, shows the raw API responses in a message dialog for troubleshooting. |
| Oldest Expense Reports to load (CutOffDate) | Expense reports dated before this date are not retrieved. |
How Authentication Works
Every call the app makes to Certify includes two headers:
x-api-key— your API Keyx-api-secret— your API Secret
These are read from the Setup card. The app tests that Base URL, API Key, and API Secret are all filled before making a call, so an incomplete setup produces a clear error rather than a failed request.
Getting Your API Key and Secret
The API key and secret are issued from your Certify/Emburse account. Obtain them from your Certify administrator or the Certify admin portal, then paste them into the Setup card. If your credentials are rotated in Certify, update them here as well.
Setting the Base URL
The default https://api.certify.com/v1/ targets the Certify v1 API. Only change this if Certify/Emburse has directed you to use a different endpoint for your account or region. The path of each request (for example expensereports or expensecategories) is appended to this Base URL automatically.
The Cut-Off Date
The Oldest Expense Reports to load date limits how far back the app reaches when downloading reports. When set, the app requests reports with a start date on or after this date. Use it to:
- Avoid importing historical reports that were already accounted for before go-live.
- Keep the report list focused and reduce the volume of API calls.
If left blank, the app retrieves all available reports (paging through results until none remain).
Debug Mode
Turn on Use Debug Mode only when investigating a problem. With it enabled, the app displays the raw JSON it receives from Certify (for example, when loading expense reports or categories). This is useful for confirming what Certify is returning, but it is noisy for everyday use — turn it off again afterward.
Testing the Connection
After entering your credentials, open Certify Expense Reports and choose Get Expense Reports. If reports load, the connection works. If you receive a contact/authorization error, re-check the key, secret, and Base URL. See Common Issues.
Tips and Best Practices
- Restrict access to the Setup card — it holds your API credentials.
- Use a dedicated Certify integration credential rather than a personal user's key where possible.
- Set a sensible cut-off date at go-live to avoid importing old data.