Farmbrite Plots & Grow Locations API

openapi: 3.2.0
info:
  title: Farmbrite API Developers Documentation Plots & Grow…
  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: Plots & Grow Locations
  description: A grow location represents where you plan to grow crops (field, greenhouse, etc) or graze animals (pasture or paddock).
paths:
  /plots:
    post:
      tags:
      - Plots & Grow Locations
      summary: Create a Plot
      description: 'Create a grow location or plot


        ### Parameters


        **title** `REQUIRED`

        The name of your grow location


        ---


        **type** `OPTIONAL`


        The type of grow location. Supported options are:


        > "Field", "Greenhouse", "Grow Room", "Pasture", "Paddock", "Other"


        Defaults to `Field`


        ---


        **layout_type** `OPTIONAL`


        How should plantings be managed and calculated. Supported options are:


        > "Planted in Beds", "Cover Crop", "Row Crops", "Other"


        Defaults to `Planted in Beds`


        ---


        **description** `OPTIONAL`


        Text describing the grow location


        ---


        **grazing_rest_days** `OPTIONAL`


        If using for grazing, the number of days that the location should be rested between grazings.


        ---


        **internal_id** `OPTIONAL`


        Custom internal ID to identify the grow location.


        ---


        **electronic_id** `OPTIONAL`


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


        ---


        **light_profile** `OPTIONAL`


        Light profile of planting area. Supported options are:


        > "Full Sun", "Full to Part Sun", "Partial Sun", "Sun to Part Shade", "Partial Shade", "Full Shade"


        ---


        **size** `OPTIONAL`


        Size in Acres/Hectares (based on account settings)


        ---


        **status** `OPTIONAL`


        Growing status of the grow location. Supported options are:


        > "Active", "Fallow", "Leased", "Other"'
      requestBody:
        content:
          application/json:
            schema:
              type: object
              example:
                description: ''
                grazing_rest_days: null
                internal_id: B40
                layout_type: Planted in Beds
                light_profile: ''
                size: 100
                status: Active
                title: Back 40
                type: Field
      parameters:
      - name: Content-Type
        in: header
        schema:
          type: string
        example: application/json
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: postPlots
      x-operation-id-source: derived
    get:
      tags:
      - Plots & Grow Locations
      summary: List Plots
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
              example:
                data:
                - id: GUID
                  description: ''
                  grazing_rest_days: null
                  internal_id: B40
                  layout_type: Planted in Beds
                  light_profile: ''
                  size: 40
                  status: Active
                  title: Back 40
                  type: Field
      operationId: getPlots
      x-operation-id-source: derived
  /plots/{plot_id}:
    get:
      tags:
      - Plots & Grow Locations
      summary: Retrieve a Plot
      parameters:
      - name: plot_id
        in: path
        schema:
          type: string
        required: true
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
              example:
                id: GUID
                copied_from: null
                created_at: '2019-01-23 02:56:46'
                description: ''
                grazing_rest_days: null
                internal_id: B40
                layout_type: Planted in Beds
                light_profile: ''
                size: 40
                status: Active
                title: Back 40
                type: Field
                updated_at: '2021-07-15 20:21:52'
      operationId: getPlotsByPlotId
      x-operation-id-source: derived
    put:
      tags:
      - Plots & Grow Locations
      summary: Update a Plot
      requestBody:
        content:
          application/json:
            schema:
              type: object
              example:
                description: Updated
      parameters:
      - name: Content-Type
        in: header
        schema:
          type: string
        example: application/json
      - name: plot_id
        in: path
        schema:
          type: string
        required: true
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: putPlotsByPlotId
      x-operation-id-source: derived
    delete:
      tags:
      - Plots & Grow Locations
      summary: Delete a Plot
      parameters:
      - name: plot_id
        in: path
        schema:
          type: string
        required: true
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: deletePlotsByPlotId
      x-operation-id-source: derived
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer