How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

farmOS Logs API

Farm activity records (activities, observations, inputs, harvests, etc.)

farmOS Logs API is one of 6 APIs that farmOS publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Logs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and a GitHub repository.

This API exposes 50 operations across 20 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 2.x.

Requests are made against a single base URL, https://{farmOS-host}/api.

50 operations 20 paths 10 schemas 10 DELETE20 GET10 PATCH10 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.x
Base URL
https://{farmOS-host}/api
Authentication
OAuth 2.0, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

farmOS Logs API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2AuthorizationCode) using the authorizationCode flow, exposing 3 scopes. It supports OAuth 2.0 (oauth2ClientCredentials) using the clientCredentials flow, exposing 3 scopes. By default, every request must be authenticated.

  • oauth2AuthorizationCode — OAuth2 Authorization Code grant for third-party integrations. Users authorize the client application to access their farmOS data.
  • oauth2ClientCredentials — OAuth2 Client Credentials grant for machine-to-machine authentication. Used when no user account is required.

Paths & Operations 50

Across 20 paths, the API surfaces 50 operations — 10 DELETE, 20 GET, 10 PATCH, 10 POST. Each is listed below with its method, path, parameters, and response codes.

Logs 50

Farm activity records (activities, observations, inputs, harvests, etc.)

GET
/log/activity
List activity logs
listActivityLogs 5 params → 200401
POST
/log/activity
Create an activity log
createActivityLog body → 201401422
GET
/log/activity/{id}
Get an activity log
getActivityLog 1 param → 200401404
PATCH
/log/activity/{id}
Update an activity log
updateActivityLog 1 param body → 200401404
DELETE
/log/activity/{id}
Delete an activity log
deleteActivityLog 1 param → 204401404
GET
/log/observation
List observation logs
listObservationLogs 5 params → 200401
POST
/log/observation
Create an observation log
createObservationLog body → 201401422
GET
/log/observation/{id}
Get an observation log
getObservationLog 1 param → 200401404
PATCH
/log/observation/{id}
Update an observation log
updateObservationLog 1 param body → 200401404
DELETE
/log/observation/{id}
Delete an observation log
deleteObservationLog 1 param → 204401404
GET
/log/input
List input logs
listInputLogs 5 params → 200401
POST
/log/input
Create an input log
createInputLog body → 201401422
GET
/log/input/{id}
Get an input log
getInputLog 1 param → 200401404
PATCH
/log/input/{id}
Update an input log
updateInputLog 1 param body → 200401404
DELETE
/log/input/{id}
Delete an input log
deleteInputLog 1 param → 204401404
GET
/log/harvest
List harvest logs
listHarvestLogs 5 params → 200401
POST
/log/harvest
Create a harvest log
createHarvestLog body → 201401422
GET
/log/harvest/{id}
Get a harvest log
getHarvestLog 1 param → 200401404
PATCH
/log/harvest/{id}
Update a harvest log
updateHarvestLog 1 param body → 200401404
DELETE
/log/harvest/{id}
Delete a harvest log
deleteHarvestLog 1 param → 204401404
GET
/log/seeding
List seeding logs
listSeedingLogs 5 params → 200401
POST
/log/seeding
Create a seeding log
createSeedingLog body → 201401422
GET
/log/seeding/{id}
Get a seeding log
getSeedingLog 1 param → 200401404
PATCH
/log/seeding/{id}
Update a seeding log
updateSeedingLog 1 param body → 200401404
DELETE
/log/seeding/{id}
Delete a seeding log
deleteSeedingLog 1 param → 204401404
GET
/log/transplanting
List transplanting logs
listTransplantingLogs 5 params → 200401
POST
/log/transplanting
Create a transplanting log
createTransplantingLog body → 201401422
GET
/log/transplanting/{id}
Get a transplanting log
getTransplantingLog 1 param → 200401404
PATCH
/log/transplanting/{id}
Update a transplanting log
updateTransplantingLog 1 param body → 200401404
DELETE
/log/transplanting/{id}
Delete a transplanting log
deleteTransplantingLog 1 param → 204401404
GET
/log/maintenance
List maintenance logs
listMaintenanceLogs 5 params → 200401
POST
/log/maintenance
Create a maintenance log
createMaintenanceLog body → 201401422
GET
/log/maintenance/{id}
Get a maintenance log
getMaintenanceLog 1 param → 200401404
PATCH
/log/maintenance/{id}
Update a maintenance log
updateMaintenanceLog 1 param body → 200401404
DELETE
/log/maintenance/{id}
Delete a maintenance log
deleteMaintenanceLog 1 param → 204401404
GET
/log/medical
List medical logs
listMedicalLogs 5 params → 200401
POST
/log/medical
Create a medical log
createMedicalLog body → 201401422
GET
/log/medical/{id}
Get a medical log
getMedicalLog 1 param → 200401404
PATCH
/log/medical/{id}
Update a medical log
updateMedicalLog 1 param body → 200401404
DELETE
/log/medical/{id}
Delete a medical log
deleteMedicalLog 1 param → 204401404
GET
/log/birth
List birth logs
listBirthLogs 5 params → 200401
POST
/log/birth
Create a birth log
createBirthLog body → 201401422
GET
/log/birth/{id}
Get a birth log
getBirthLog 1 param → 200401404
PATCH
/log/birth/{id}
Update a birth log
updateBirthLog 1 param body → 200401404
DELETE
/log/birth/{id}
Delete a birth log
deleteBirthLog 1 param → 204401404
GET
/log/lab_test
List lab test logs
listLabTestLogs 5 params → 200401
POST
/log/lab_test
Create a lab test log
createLabTestLog body → 201401422
GET
/log/lab_test/{id}
Get a lab test log
getLabTestLog 1 param → 200401404
PATCH
/log/lab_test/{id}
Update a lab test log
updateLabTestLog 1 param body → 200401404
DELETE
/log/lab_test/{id}
Delete a lab test log
deleteLabTestLog 1 param → 204401404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are LogAttributes (11 properties), LogRelationships (7 properties), LogData (5 properties), LogCollection (4 properties). Each schema is shown below with its type and property counts.

LogAttributes
object
Common attributes shared by all log types
11 properties
JsonApiRelationship
object
2 properties
LogCollection
object
4 properties
LogRequest
object
1 property 1 required
JsonApiError
object
1 property
LogData
object
5 properties 2 required
JsonApiLinks
object
2 properties
JsonApiRelationshipData
object
2 properties
LogRelationships
object
Common relationships shared by all log types
7 properties
LogResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

farmos-logs-api-openapi.yml Raw ↑

Other APIs farmOS publishes across the network.

farmOS Assets API
farmOS Plans API
farmOS Quantities API
farmOS Server Info API
farmOS Taxonomy API
Where this information came from

This is an independent, third-party profile of farmOS Logs API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.