ANBIMA Feed IMA-ETF is a customized package composed of RESTFul APIs based on the HTTP protocol for providing data to ETFs (Exchange Traded Funds) licensed by ANBIMA for the purpose of using an index of the IMA family. It has information of the licensed index, such as daily results, daily composition, liquidity statistics of components, intraday unit prices and results and theoretical portfolios projections. The indices currently available in ANBIMA Feed are IMA-B, IMA-B 5+, IMA-B 5 P2 and IRF-M P2.
The methodologies of all publications are available on ANBIMA’s Portal.
As a standard, our APIs present the results for all IMA family indices acquired. However, it is possible to make queries by filtering one or more indices.
Below, there is a “from-to” to help when making queries through our URIs:
|IMA-B 5 P2|
Our APIs were developed using the OpenAPI Specification, which will give the developer greater flexibility in consumption
Advantages of using Swagger:
- Try it out: allows you to perform initial tests directly on our platform
- REST: standard for easy integration
Learn about our environments
Our APIs can be accessed through two environments: Sandbox and Production.
The Sandbox environment can be used for general service tests, such as verifying the response format of a resource specific of the API. Currently, the data returned will be fixed and fictitious.
On the other hand, the official information can be obtained through the Production environment.
How to make calls requests to our API resources?
In practice, a call to this API always considers the URI model below:
api.anbima.com.br (Production) or
Therefore, the URI to be used to access any API of ANBIMA Feed IMA-ETF would be:
Remember that all this API’s resources are private and can only be accessed on Sandbox and Production environments through OAut 2 authentication standard (detailed in the Authentication section).
|400||Bad request. Please, verify the request URI.|
|401||Request needs authentication. Probably, “base64 code” sent by ANBIMA may have been created with invalid credentials or may be missing in the request header.|
|405||Method not allowed. The request method must be POST. Please verify.|
|406||Invalid Content or Content-Type. Please, verify the content in the request body (it is expected a JSON containing the notification fields).|
|5XX||Unexpected server internal error.|
|200||Successful consultation. Data available and reported in the response body.|