Farmbrite Climate > Gauges API

Climate Gauges are used to track the location of climate and enviromental data recorded (Climate Logs). Each gauage can represent a physical or logcial area of your propery where you want to track climate data.

GitHub OpenAPI

Operations 5

POST /climate_gauges Create a Gauge #
GET /climate_gauges List Climate Gauges #
GET /climate_gauges/{gauge_id} Retrieve a Gauage #
PUT /climate_gauges/{gauge_id} Update a Gauge #
DELETE /climate_gauges/{gauge_id} Delete a Gauge #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/farmbrite:farmbrite-climate-gauges-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

farmbrite-climate-gauges-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Farmbrite API Developers Documentation Climate > Gauges API
  description: '# Overview


    Welcome to the Farmbrite API. You can find out more about Farmbrite at

    www.farmbrite.com


    If you need help, check out our help center at help.farmbrite.com or email us at dev@farmbrite.com. ## API Reference


    The Farmbrite API allows authorized users programatic access to their account data in order to facilitate the integration of this data with other systems and service. The API is organized around REST standards. The API uses resource-oriented URLs and returns JSON-encoded responses. It uses standard HTTP response codes, authentication, and verbs. > Base URL


    ```

    https://api.farmbrite.com/v1


    ```


    # Authentication


    Farmbrite offers 2 authentication options for accessing the API both utilizing Personal Access Tokens (PATs) for enabling access to the API. Access Tokens (API Keys) are associated with an individual user in your account and inherit that user''s role and permissions. You can find the Access Token on the user profile page under API Key. When building an integration we recommend setting up a separate API user for the integration and changing the API KEY on a regular basis. Remember to keep your Access Tokens secret; treat them just like passwords! They act on your behalf when interacting with the API, with the same permissions and access as the user has. _Don''t hardcode them into your programs_. Instead, choose to store them as environment variables. ### Bearer Token


    To make a request to the API include the Authorization Bearer header with your request and include your Access Token (API KEY) as the value. Access Token and API KEY are used interchangeably through out the documentation. > Example cURL request authenticating with Bearer Token authentication


    ```

    curl https://api.farmbrite.com/v1/tasks \

    -H "Authorization: Bearer ACCESS_TOKEN"


    ```


    ### API Key


    Alternatively to using the Bearer Token authorization method, you can provide an API KEY as a header with your request. Use the header `api_key` with a value of your Access Token (API KEY). > Example cURL request authenticating with API Key header authentication


    ```

    curl https://api.farmbrite.com/v1/tasks \

    -H "api_key: ACCESS_TOKEN"


    ```


    # Errors


    Sadly, sometimes requests to the API fail. Failures can occur for a wide range of reasons. In all cases, the API should return an HTTP Status Code indicating the nature of the failure. | Code | Meaning | Description |

    | --- | --- | --- |

    | 200 | Success | The request was successful. If applicable the data it will be available in the data field at the top level of the response body. |

    | 400 | Bad Request | Typically caused by a missing or malformed parameter. Check the documentation and your request and try again. |

    | 401 | Unauthorized | No access token or an invalid access token was provided with the request. The error can also occur if the user or account is invalid or does not have access to this resource. |

    | 403 | Forbidden | The authentication and request syntax was valid but the server is refusing to complete the request. This can happen if you access resources that the user or account does not have access to. |

    | 404 | Not Found | Either the method and path supplied do not specify a known action or the object related to the request does not exist. |

    | 429 | Too Many Requests | You have exceeded one of the rate limits in the API. See the Rate Limits section for more information. |

    | 500 | Internal Server Error | There was a problem on Farmbrite''s side which was logged and reported to our technical team. You can retry, but if the problem continues please contact support. |


    Details about errors can sometimes also be found in the ''message'' property at the root level of the JSON response body. # Pagination


    In order to optimize performance, all list methods in the API will limit the total response data to a certain number of records and return the data in chunks (pages). API responses will include information about the total records available, the current page and total pages.'
  version: 1.0.0
  x-logo:
    url: https://static.farmbrite.com/assets/www/images/logo.png
    backgroundColor: '#FFFFFF'
    altText: Farmbrite
  termsOfService: https://www.farmbrite.com/terms
  contact:
    name: Farmbrite
    url: https://developers.farmbrite.com
    email: dev@farmbrite.com
servers:
- url: https://api.farmbrite.com/v1
security:
- bearerAuth: []
tags:
- name: Climate > Gauges
  description: Climate Gauges are used to track the location of climate and enviromental data recorded (Climate Logs). Each gauage can represent a physical or logcial area of your propery where you want to track climate data.
paths:
  /climate_gauges:
    post:
      tags:
      - Climate > Gauges
      summary: Create a Gauge
      description: 'Create a climate gauge


        ### Parameters


        **description** `OPTIONAL`


        A note or summary for the gauge


        ---


        **electronic_id** `OPTIONAL`


        Electronic ID - useful to set if using an RFID or barcode scanner to search for for sync data with Farmbrite.


        ---


        **latitude** `OPTIONAL`


        The latitude of gauge location


        ---


        **longitude** `OPTIONAL`


        The latitude of gauge location


        ---


        **name** `OPTIONAL`


        The name or title for the gauge


        ---


        **place_id** `OPTIONAL`


        The map location ID (animal enclosure, building, etc) that the gauge is located


        ---


        **plot_id** `OPTIONAL`


        The plot or grow location ID that the gauge is located


        ---'
      requestBody:
        content:
          application/json:
            schema:
              type: object
              example:
                name: Greenhouse Gauge
                description: Temperature and humidity gauge for greenhouse
                electronic_id: ''
                latitude: 90
                longitude: 0
                plot_id: Farmbrite Grow locaiton ID
      parameters:
      - name: Content-Type
        in: header
        schema:
          type: string
        example: application/json
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: postClimateGauges
      x-operation-id-source: derived
    get:
      tags:
      - Climate > Gauges
      summary: List Climate Gauges
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
              example:
                success: true
                cached: false
                message: ''
                total_records: 1
                current_page: 1
                limit: 25
                total_pages: 1
                data:
                - id: Gauge ID
                  created_at: '2023-03-17 21:39:58'
                  description: ''
                  latitude: null
                  longitude: null
                  name: Sensor 1A
                  place_id: null
                  plot_id: Plot ID
                  updated_at: '2023-03-17 21:39:58'
      operationId: getClimateGauges
      x-operation-id-source: derived
  /climate_gauges/{gauge_id}:
    get:
      tags:
      - Climate > Gauges
      summary: Retrieve a Gauage
      parameters:
      - name: gauge_id
        in: path
        schema:
          type: string
        required: true
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
              example:
                id: Gauge ID
                created_at: '2023-03-17 21:39:58'
                description: ''
                latitude: null
                longitude: null
                name: Sensor 1A
                place_id: null
                plot_id: Plot ID
                updated_at: '2023-03-17 21:39:58'
      operationId: getClimateGaugesByGaugeId
      x-operation-id-source: derived
    put:
      tags:
      - Climate > Gauges
      summary: Update a Gauge
      requestBody:
        content:
          application/json:
            schema:
              type: object
              example:
                name: Gauge 001A
      parameters:
      - name: Content-Type
        in: header
        schema:
          type: string
        example: application/json
      - name: gauge_id
        in: path
        schema:
          type: string
        required: true
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: putClimateGaugesByGaugeId
      x-operation-id-source: derived
    delete:
      tags:
      - Climate > Gauges
      summary: Delete a Gauge
      parameters:
      - name: gauge_id
        in: path
        schema:
          type: string
        required: true
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: deleteClimateGaugesByGaugeId
      x-operation-id-source: derived
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer