Farmbrite Notes API

openapi: 3.2.0
info:
  title: Farmbrite API Developers Documentation Notes 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: Notes
  description: 'Notes are embedded resources that are used by a variety of core resources. Specifically you can access notes for resources:


    - Livestock `/animals`


    - Livestock Groups (Create Only) `/livestock_groups`


    - Grow Locations `/plots`


    - Plant Types `/plants`


    - Plantings `/crops`


    - Equipment `/tools`


    - Inventory Types `/inventory_types`


    To create or access notes for a record, simply append ''/notes'' to the end of the resource path.


    For example: \[GET\] /animals/:animal_id/notes will fetch the notes for this animal (based on animal id). and \[POST\] /animals/:animal_id/notes will add a note to this animal.'
paths:
  /{resource_name}/{resource_id}/notes:
    post:
      tags:
      - Notes
      summary: Create a Note
      description: "Create a note\n\n### Parameters\n\n**description** `REQUIRED`\n\nThe contents of the note that you want to record for the parent resource\n\n* * *\n\n**date** `OPTIONAL`\n\nThe date the note was captured. Defaults to today.\n\n* * *\n\n**category** `OPTIONAL`\n\nThe category for the note. For example, for livestock you might use one of the following categories:\n\n> \"Breeding\", \"Deworming\", \"General\", \"Grazing\",\" Grooming\", \"Injury\", \"Medication\",\" Supplement\", Vaccination\", \"Veterinarian\", \"Other\"\n\n* * *\n\n**keywords** `OPTIONAL`\n\nA comma delimited list of keywords, tags or labels to easily search for similar notes\n\n* * *\n\n\uFEFF**longitude** `OPTIONAL`\n\nLongitude of the note location\n\n* * *\n\n**latitude** `OPTIONAL`\n\nLatitude of the note location"
      requestBody:
        content:
          application/json:
            schema:
              type: object
              example:
                date: '2023-08-01'
                description: Note details
                category: Other
                keywords: test
      parameters:
      - name: Content-Type
        in: header
        schema:
          type: string
        example: application/json
      - name: resource_name
        in: path
        schema:
          type: string
        required: true
      - name: resource_id
        in: path
        schema:
          type: string
        required: true
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: postByResourceNameByResourceIdNotes
      x-operation-id-source: derived
    put:
      tags:
      - Notes
      summary: Update a Note
      requestBody:
        content:
          application/json:
            schema:
              type: object
              example:
                description: Note Update
      parameters:
      - name: Content-Type
        in: header
        schema:
          type: string
        example: application/json
      - name: resource_name
        in: path
        schema:
          type: string
        required: true
        example: '{{resource_name}}'
      - name: resource_id
        in: path
        schema:
          type: string
        required: true
        example: '{{resource_id}}'
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: putByResourceNameByResourceIdNotes
      x-operation-id-source: derived
    get:
      tags:
      - Notes
      summary: List Notes
      parameters:
      - name: resource_name
        in: path
        schema:
          type: string
        required: true
        example: '{{resource_name}}'
      - name: resource_id
        in: path
        schema:
          type: string
        required: true
        example: '{{resource_id}}'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
              example:
                data:
                - id: GUID
                  category: CATEGORY
                  created_at: '2022-03-10 00:22:51'
                  created_by: USER
                  date: '2022-03-10'
                  description: description
                  keywords: ''
                  latitude: null
                  longitude: null
                  updated_at: '2022-03-10 00:22:51'
      operationId: getByResourceNameByResourceIdNotes
      x-operation-id-source: derived
  /{resource_name}/{resource_id}/notes/{note_id}:
    get:
      tags:
      - Notes
      summary: Retrieve a Note
      parameters:
      - name: resource_name
        in: path
        schema:
          type: string
        required: true
        example: '{{resource_name}}'
      - name: resource_id
        in: path
        schema:
          type: string
        required: true
        example: '{{resource_id}}'
      - name: note_id
        in: path
        schema:
          type: string
        required: true
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
              example:
                id: GUID
                category: CATEGORY
                created_at: '2022-03-10 00:22:51'
                created_by: USER
                date: '2022-03-10'
                description: description
                keywords: ''
                latitude: null
                longitude: null
                updated_at: '2022-03-10 00:22:51'
      operationId: getByResourceNameByResourceIdNotesByNoteId
      x-operation-id-source: derived
    delete:
      tags:
      - Notes
      summary: Delete a Note
      parameters:
      - name: resource_name
        in: path
        schema:
          type: string
        required: true
        example: '{{resource_name}}'
      - name: resource_id
        in: path
        schema:
          type: string
        required: true
        example: '{{resource_id}}'
      - name: note_id
        in: path
        schema:
          type: string
        required: true
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: deleteByResourceNameByResourceIdNotesByNoteId
      x-operation-id-source: derived
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer