The Ethixbase360 API is a RESTful interface that allows you to interact programmatically with your EB360 platform and integrate it with other systems such as Salesforce, ServiceNow, HubSpot, Omnitrack or Coupa.
It follows a standard request-response model: you send a request to the API, and it returns data (or an error message) based on the outcome.
Like all RESTful APIs, the EB360 API is pull-based - it does not push data to other systems. However, we are actively extending Ethixbase360’s capabilities to support push-based delivery of API data. This will be introduced in a future release and will enable EB360 to proactively send updates to external systems.
What can the API do?
Here are some examples of what you can do using the EB360 API:
- Onboard new third parties.
- Retrieve and manage third-party data, including profiles, risk ratings, and custom attributes.
- Retrieve the latest consolidated screening data for third parties.
- Order and retrieve Enhanced Due Diligence (EDD) reports for third parties.
- Search for third parties using filters like risk status, country, or creation date.
- Access user and platform configuration data, such as user lists and available languages.
How it works
- The EB360 API follows standard RESTful principles.
- You make HTTP requests (e.g. GET, POST, PUT, DELETE) to interact with EB360 data.
- Responses are returned in JSON format, along with relevant status and error codes.
Developers will need to write code to consume the API and connect it to other systems.
Viewing the API documentation
The best way to access the API documentation is from your EB360 platform.
- Log in to your EB360 platform.
- Append /api/v1 to the base URL. For example: https://EB360Platform123.com/api/v1
- The Ethixbase EB360 OpenAPI specification is displayed.
When you access the specification in this way, it will be the correct version for your platform and you can test API calls directly from the specification.
Alternatively:
If you are not logged in to an EB360 platform, you can also view a general version of the API spec here:
Note: when you access the API specification in this way, you will not be able to test API calls - and the version may not match your platform.
Comments
0 comments
Please sign in to leave a comment.