The Visipec API is a REST API. Responses to requests are returned in JSON or Excel format. All communication between server and client are require an HTTPS protocol to increase security in information transmission.
For specific technical documentation about Visipec API endpoints and parameters, visit API Documentation.
VISIPEC was developed specifically for meatpacking companies (and monitoring companies) in Brazil to help strengthen supply chain management systems and improve the decision-making process for cattle purchases. It is freely available to the meatpacking industry in Brazil, and is intended to complement the meatpacker’s existing supply chain monitoring and traceability systems for direct suppliers by providing enhanced visibility to the complex network of indirect suppliers. It is not intended to replace existing systems. VISIPEC can also provide aggregate information and summary report for retailers, supermarkets, banks, investors, and financial intuitions.
Interested parties can contact Simon Hall (halls@nwf.org), or Lisa Rausch (lisa@visipec.com) to discuss receiving access credentials to use the Visipec API.
When sending a request, please include the following elements of information:
To encourage adoption of the Visipec API, we have developed a simple API Client program that can be used to communicate directly with the Visipec API. Users will be required to have valid access credentials for the Client to communicate successfully with the Visipec API.
The Visipec API Client is available for Windows and Mac operating systems. Instructions for downloading and using the Visipec API Client follow. Use the Windows or Mac instructions below based on the operating system of your computer.
If you experience any issues setting up your Visipec API Client, please email your issues to support@visipec.com.
See Operating the Visipec API Client (Command Line Options) section below for details on how to use the Client now that you have it installed.
If you experience any issues setting up your Visipec API Client, please email your issues to support@visipec.com.
See Operating the Visipec API Client (Command Line Options) section below for details on how to use the Client now that you have it installed.
Note: Output of the Viispec API is JSON structured data. If you do not already use a JSON viewer and would like to view the data in an easy-to-read interface, free JSON viewers exist, e.g., http://jsonviewer.stack.hu or https://jsoneditoronline.org.
Name | Expectected Input | Required | Description |
---|---|---|---|
-out | outputFilePath | No | Location to save response from server to. If left blank, output will be printed to the screen. |
Name | Expectected Input | Required | Description |
---|---|---|---|
-property | carNumbers | Yes | Comma separated list of CAR numbers to request information on. |
-out | outputFilePath | No | Location to save response from server to. If left blank, output will be printed to the screen. |
-bp-start | bpStartDate | No | Transaction start date used to calculate Boas Practicas deforestation date ranges |
-bp-end | bpEndDate | No | Transaction end date used to calculate Boas Practicas deforestation date ranges |
Name | Expectected Input | Required | Description |
---|---|---|---|
-property-summary | carNumbers | Yes | Comma separated list of CAR numbers to request information on. |
-out | outputFilePath | No | Location to save response from server to. If left blank, output will be printed to the screen. |
-bp-start | bpStartDate | No | Transaction start date used to calculate Boas Practicas deforestation date ranges |
-bp-end | bpEndDate | No | Transaction end date used to calculate Boas Practicas deforestation date ranges |
Name | Expectected Input | Required | Description |
---|---|---|---|
-slaughterhouse | sifNumber | Yes | A single SIF number. |
-out | outputFilePath | No | Location to save response from server to. If left blank, output will be printed to the screen. |
-bp-start | bpStartDate | No | All transactions between suppliers and the SIF will be after this date. This date is also used to calculate Boas Practicas deforestation date ranges. |
-bp-end | bpEndDate | No | All transactions between suppliers and the SIF will be before this date |
-car | carFilter | No | A comma separated list of CAR numbers to filter output on |
Name | Expectected Input | Required | Description |
---|---|---|---|
-slaughterhouse-summary | sifNumber | Yes | A single SIF number. |
-out | outputDirectoryPath | No | Directory to save response from server to. If left blank, output will be printed to the screen. |
-bp-start | bpStartDate | No | All transactions between suppliers and the SIF will be after this date. This date is also used to calculate Boas Practicas deforestation date ranges. |
-bp-end | bpEndDate | No | All transactions between suppliers and the SIF will be before this date |
-car | carFilter | No | A comma separated list of CAR numbers to filter output on |
For specific technical documentation about Visipec API endpoints and parameters, visit https://api.visipec.com/api-documentation.html.
To initiate a valid user session with the Visipec API, users must first authenticate to the system using a POST request to the Jwt endpoint. Valid requests will receive a Jwt bearer token in response. This Jwt bearer token can be used to submit future requests to the Visipec API until the session expires.
For example, using a common generic client such as curl, a user could send the following request to the Visipec API:
curl -X POST "https://api.visipec.com/api/Jwt" -H "accept: application/json" -H "Content-Type: application/json" -d "{ \"Token\": \"YOUR-TOKEN-HERE\"}"
The authentication POST above will return a Jwt (JSON Web Tokens) Bearer token that will be required for any valid request to Visipec API property and slaughterhouse endpoints.
Note that the Slaughterhouse endpoint is only available with permission from the Visipec API administrators. Please contact Simon Hall (halls@nwf.org), or Lisa Rausch (lisa@visipec.com) to discuss receiving access to search data related to a specified SIF number.