just reading through the documentation of the API and was wondering the the API Reference get deprecated with the version 1.3. It that correct ?
We want to call the Farmbot Web App with an external App using the Farmbot API (REST, JSON…)
Could you stick me to the right documentation how to do that or explain how to do that ?
The latest REST API documentation is available here. I have updated the documentation just now so it is the most up-to-date version for my.farmbot.io.
One thing to keep in mind is that we use the REST server only for data storage. This means that you cannot control FarmBot via REST. If you wish to write an application that will control a FarmBot, you will need to use the MQTT server.
Post it here, if anybody else would have the same question.
Now I got the token and will continue with testing the REST API.
Will give you feedback how it works within our app.
Hi Rick,
I’ve started to make a swaggerDoc-File for the rest-api to improve the overview (and documentation).
Do you have an idea for the correct directory for such a thing in the git-repo?
Here a short summary about swagger:
it’s an REST-API-Specification (OAS / OpenAPI) (this is the swaggerDoc-File - json or yaml)
Code-First: Annote the endpoints in source-code and use a swagger-framework to generate a swaggerDoc and to generate an documented HTML-RestClient for the API
Yes, swagger has a ruby-lib unfortunately I’m not very familiar with ruby so I decided to start with a Design-First approch.
In the long run it would be cool to have a well documented swagger-ui with a mock-farmbot. That would decrease the barrier to develop software against the farmbot REST-API (IMHO).
@fafi That’s great to hear! A swagger/ folder at the project root might work fine. Did you put it up on Github yet?
I’m familiar with Swagger, and would probably chose it as our documentation format when we have the time to implement. I’ve tried to adopt it in the past, but my main reason for not using it is simply a lack of time.
The API is 4 years old, so there are a lot of edge cases that must be documented.