REST Endpoints |
Scroll |
By installing the Therefore™ BC Connector, the following endpoints are added:
•TFDocuments
•ProcessingJournals
Those endpoints are neither part of the OData, nor the v2.0 API of Business central. Depending on your system, they are reachable under those URLs:
https://bcserver:7048/bc/api/therefore/connector/v1.0/tfdocuments
https://bcserver:7048/bc/api/therefore/connector/v1.0/companies(company-id)/tfdocuments
https://api.businesscentral.dynamics.com/v2.0/environment-guid/api/therefore/connector/v1.0/companies(company-id)/tfdocuments
https://api.businesscentral.dynamics.com/v2.0/environment-guid/sandbox/api/therefore/connector/v1.0/companies(company-id)/tfdocuments
(“tfdocuments” was chosen as a sample endpoint here)
Company-ID:
To find out the company ID, you can call the following API function:
https://api.businesscentral.dynamics.com/v2.0/environment-guid/api/v2.0/companies
https://bcserver:7048/bc/api/v2.0/companies
It is a GET call without a body and requires the same authorization as the other API calls.
Environment-GUID:
To find out your “environment-guid”, click on “? -> Help & Support”
Then scroll down to “Troubleshooting” to find your Azure AD Tenant ID
Installation
If you have trouble reaching one of the Therefore™ endpoints, please ensure that the following settings are turned on:
• Enable API Service
• Enable OData Services