Contractors.es icon

Contractors.es

Interact with Contractors.es API

Actions995

Equipment History Api → Post Api Assets Equipment History

AI-generated

Summary

Posts an equipment history record to the Contractors.es API. Set the fields you want to send; fields left at DO_NOT_SET are omitted from the request body.

Inputs

  • Rented — Rented status or value.
  • Equipment Id — Equipment identifier.
  • Rented Equipment No — Number for the rented equipment.
  • Rented Equipment Description — Description of the rented equipment.
  • Rental Vendor Id — Rental vendor identifier.
  • Rental Cost — Rental cost.
  • Rental Cost Currency — Currency for the rental cost.
  • Rental Cost Interval — Interval for the rental cost.
  • Total Cost — Total cost.
  • Total Cost Currency — Currency for the total cost.
  • Responsible — Select employee, subcontractor, or other as the responsible party.
  • Employee Id — Employee identifier.
  • Subcontractor Id — Subcontractor identifier.
  • Responsible Other — Specify another responsible party.
  • Assign — Assignment value.
  • Record Type — Select a project or company record type.
  • Record Id — Identifier for the associated record.
  • Date — History record date.
  • Est Return Date — Estimated return date.
  • Return Date — Return date.
  • Returned In The Same Condition — Value indicating whether the equipment was returned in the same condition.
  • What Is Wrong — Description of any problem with the equipment.
  • What Is Wrong Photos — Photo data or reference for reported equipment problems.
  • Meter Value Before — Meter reading before use.
  • Meter Value After — Meter reading after use.
  • External Id — External identifier for the history record.
  • Request Options — Optional HTTP settings: batch size and interval, whether to accept invalid SSL certificates, proxy, and request timeout.

Output shape

A response from the Contractors.es API for the created equipment history record.

The source pack shows the node building an API request but does not define or transform this operation’s response shape.

Examples

Example 1: Skipping fields

Keep unused fields at their default value, DO_NOT_SET; the node omits those fields from the request body.

Example 2: Setting the responsible party

Choose Employee, Subcontractor, or Other, then populate the corresponding ID or other-description field as applicable.

Links

Discussion