BREX by kompany® provides real-time access to structured, official and authoritative commercial register data, including company filings covering more than 55 million companies in 80+ countries and jurisdictions.
The BREX API enables you to fully automate the retrieval of company data from commercial registers worldwide for your KYC, AML and enhanced due diligence (EDD) processes. Or to prefill your internal CRM or ERP system with company vitals to ensure up to date and correct information in your supplier or customer databases.
It provides instant access to:
With only one lightweight RESTful API to worry about, integration is easy and cost-efficient.
Client or supplier onboarding: automated retrieval of company vitals and commercial register extracts enable a rapid business verification based on the official source data. E.g. pre-fill register number, company name, address, status, managing director, etc based on the data filed with the commercial register.
Regulatory required compliance checks: automated regular checks of the complete customer base including access to lodged financials to comply with regulatory stress tests and to remediate business partner data stored in the internal systems.
Payment merchant verification: payment providers need to verify merchants before providing access to their platforms to them. Automation of this process can significantly cut the time required for merchant verification and onboarding and ensure that no losses are occurred as a result of missed transactions.
Customized solutions: for specific customer requirements or inhouse applications, we also offer customized solutions to improve efficiency or add value to workflows or processes. For more information contact email@example.com
We cover over 80+ countries and jurisdictions today. Furthermore, we offer a concierge service through which we provide additional commercial register information on companies for a total of 115 jurisdictions quickly and efficiently.
If you have any questions, please do let us know - we can clarify any points and are always happy to work with you to find a proposal to meet your requirements. Contact with us at firstname.lastname@example.orgClaudia Prkna (Solutions Specialist)
We'd love to hear from you. Fill out the form below with some info about your project.
The BREX API is a lightweight RESTful webservice which can be used to search for corporate and related information, and to order and retrieve documents. Requests are sent through an HTTPS channel, the reply will be in JSON for data or PDF for report delivery – further formats may be added in future. The content and format of a response varies with the request and chosen subscription model, examples are given in the appendix.
The API is separated into logical functional groups which follow the general format of:
It is important to note that parameter1 to parameterX may possibly include reserved URI characters, and must therefore be URL encoded to the current standard (RFC3986). Any components of the URL preceding the parameter sections will not require encoding, but will also be defined in such a way that encoding them would have no effect.
The valid 'object' values at the time of writing are:
Valid 'method' values are:
BREX Enterprise API uses a 'live' online documentation method – this allows readers to see the format of the request URLs, any parameters, the actual URLs called and the structure of the responses. It is also synchronized with the API code, so it is always correct, and even allows the API to be driven via the website, which makes testing a much simpler operation that conventional techniques. The information supplied by this live documentation can assist greatly in writing one's own interface to the BREX API. This documentation is available to anyone with an API key and can be accessed at: http://docs.brex.io/active-docs
BREX Enterprise API uses a simple key authentication mechanism over HTTPS - this is safe because your API key is securely encrypted by the SSL channel. The easiest way to test the API is to use the online live documentation – this is a web page which allows you to test the various API methods and handles all the communications for you, whilst showing you the appropriate URLs. Brex will provide client code in php and java in due course.
When you are ready to write code to access the API, you simply pass your API key as an HTTP header called user_key. This key is used by the API to determine who you are, your access rights and your costs - keep this key secret and safe!
Your API key can be regenerated by clicking on the Regenerate button on your dashboard page.
Note: Only one API key may be active on an account per plan at a time. If you choose to regenerate your API key, your services will not work until you’ve updated all references to your API key. There is only one API key per plan. Regenerating the key will regenerate it for all users.
Brex Enterprise API currently returns results only JSON. If the accept header is specified it should be application/json, but will be ignored. Including this header, however, will future proof your client code.
Brex Enterprise API currently returns results only JSON. If the content-type header is specified it should be application/json, but will be ignored. Including this header, however, will future proof your client code.
Content-Type: application/json; charset=utf-8 Accept: application/json
If your JSON or XML request is invalid, the API will respond with a status code 400 Bad Request. This commonly occurs when ampersands are not correctly encoded in the text of your request. Please inspect the body of the response for more details regarding the error. However, please note that at the time of writing there are no API methods that correspond to a 'create' or 'update' request -therefore this is for future reference only.
Every request includes an HTTP status code with the result. The status code should examined before the response. The online documentation provides up to date status code information, however in general the response codes can be interpreted as:
The API method calls are documented in the online system, but the general object structure and sequence is as described below:
At the time of writing there are 4 basic objects – Company, Product, ProductOrder and ProductOrderNotifier.
A typical use case would be:
Note the status checking here is done via polling. There is an alternative method by using a ProductNotifier. This allows BREX to notify the customer when a product is ready. To use a ProductNotifier, replace step (6) with the following:
The use of a notifier does not preclude the polling method but is more efficient for everybody.
Enter your API key here to test our API service.If you don't have an API key yet don't enter anything, make sure to search for the available testdata provided in BREX API Technical Documentation on page 8.
Enter your API key here.