trim Endpoint

The POST trim Dairy cattle typically have their hooves inspected and, if necessary, trimmed every 4–6 months. A strategic hoof-trimming program might evaluate hooves before first calving, between 60 and 150 days in milk, and before dry-off. endpoint allows VAS partners to share TRIM Dairy cattle typically have their hooves inspected and, if necessary, trimmed every 4–6 months. A strategic hoof-trimming program might evaluate hooves before first calving, between 60 and 150 days in milk, and before dry-off. event details to PULSE. Data provided includes the following:

Date of hoof trim Dairy cattle typically have their hooves inspected and, if necessary, trimmed every 4–6 months. A strategic hoof-trimming program might evaluate hooves before first calving, between 60 and 150 days in milk, and before dry-off. event.
Additional remarks or information about the treatment.

Dairy cow hoof trimming is generally done semi-annually as a preventative treatment (to avoid lameness Lameness includes any abnormality which causes an animal to change the way it walks, and can be caused by a range of foot and leg conditions, including hoof ailments, hock damage, bruising, sores, or cuts.), or may also be used to treat specific conditions, such as digital dermatitis.

NOTE: This endpoint requires Bulk Data Access.

https://platform-vendor-api.vas.com/locations/com.vas.dairies.id/{location-id}/animals/{animal-id}/events/trim
PATH PARAMETERS
{location-id}* integer	Location identifier. For routes with “com.vas.dairies.id”, {location-id} is a VAS-specific dairy id, commonly referred to as {dairyId} when not part of an ICAR International Committee for Animal Recording (ICAR) is a global organization focused on the standardization of animal identification, recording, genetic evaluation, and data management. location scheme.
{animal-id}* integer	Animal identifier. For routes with “com.vas.animals.id”, {animal-id} is a VAS-specific A data value that originates from the VAS product line. dairy cow id, commonly referred to as {dairyCowId} when not part of an ICAR identification scheme.
* Required

OTHER PARAMETERS In addition to path parameters and the standard Authorization and API Key header parameters, the following are also required:
Content-Type	application/json
Request body*	Formatted JSON that includes the values to POST. See the Sample Request below.
* Required

Sample Request (cURL)

curl -X POST 'https://platform-vendor-api.vas.com/locations/com.vas.dairies.id/{location-id}/animals/{animal-id}/events/trim' \
-H 'Authorization: bearer {authorization token}' \
-H 'X-API-Key: {API key}'  \
-H 'Content-Type: application/json'  \
--data-raw ' 
  "member": {
        "eventDateTime": "2020-12-04T20:06:41.038Z",
        "remark": "dermatitis"
    }
}

Request Schema

Data Point	Data Type	Definition
eventDateTime*	string	Date/time stamp (YYYY-MM-DDThh:mm:ss in 24-hour UTC Coordinated Universal Time, also known as Greenwich Mean Time (GMT) time) of when the event occurred. Learn more about VAS Developer API Date/Time Formatting.
remark	string	Additional information on the event, which may be automatically generated by PULSE and/or DairyComp 305 or manually entered. The remark must not exceed 16 characters.
* Required

HTTP Status Codes & Errors

Status Code/Error	Description
`200 OK`	Standard response for a successful HTTP request.
`201 Created`	A method successfully created a resource.
`202 Accepted`	The server accepted the request and will execute it at a later point.
`204 No Content`	The server successfully executed the method but returns no response body.
`400 Bad Request`	Bad request. Depending on the endpoint, additional error details may be sent in the response. Use the strategies below to troubleshoot the error: Check the request for any typos. Check the syntax of the request and verify the parameters provided fall within the expected range. For POST endpoints, verify that the request adheres to the logic of the VAS Developer API: Events may only be added to an animal's current lactation. Events cannot be added to animals in a sold/died status. NOTE: The resource URI is case-sensitive. If you are encountering unexpected 400 errors, check your URI for correct capitalization of resource names.
`401 Unauthorized`	Authentication failed due to invalid authentication credentials.
`403 Forbidden`	You are not permitted to access this resource.
`404 Not Found`	The resource could not be found. It is possible that the resource has been moved or deleted, or that there is a typo in your request.
`405 Method Not Allowed`	The requested method and resource are not compatible.
`429 Too Many Requests`	You sent too many requests within a given period and exceeded the rate limit.
`500 Internal Server Error`	A VAS server error has occurred and the request cannot be fulfilled.
`502 Bad Gateway`	The server did not receive a timely response from another server.
`503 Service Unavailable`	The server is not available, usually due to overloading or maintenance issues.
`504 Gateway Timeout`	The server, while acting as a gateway or proxy, cannot get a response in time.

< Return to ANIMALS Resource