EZRentOut

EZRentOut treats a rental order as a small state machine with money attached, and that is the useful way to think about automating it. An order is created, items are added, the items are booked across a date range, the kit is rented out, and it comes back or it is sold. Each of those transitions is its own operation: Book Order reserves, Cancel Order Booking releases back to available stock, Rent Out Order sends equipment out and starts the rental clock with separate billing dates where the commercial terms differ from the physical ones, Return Order brings it back in full or in part with late fees and an optional payment, and Sell Order converts the hire into a sale. The pricing layer sits alongside rather than inside those transitions, which is what makes it automatable: Apply Coupons To Order, Apply Taxes To Order, Add Order Custom Entry for delivery, cleaning or fuel, Charge Order Damages for kit returned damaged, Add Sub Rental To Order for equipment sourced from another supplier, and Charge Order Payment and Void Order Payment for the money itself. The customer side is equally explicit, separating individual customers from business accounts and from the business contacts who order on their behalf.

Several conventions here will bite a flow that assumes otherwise, and they are worth designing around from the start. Dates are month, day, year and times are hours and minutes, throughout the whole API, regardless of what your account displays. Bundles are addressed inside item lists with a -b suffix, so 2 is item number two and 25-b is bundle twenty five. Order numbers and item numbers are the ones shown in the EZRentOut interface, not internal database identifiers. Partial returns key their quantities by order line item identifier, which you read from Get Order Details. Credit card is not an accepted payment method through the API, and a credit card payment cannot be voided through it either. Custom entries cannot be added to sold, void, completed or canceled orders. Most consequentially, which order fields are editable depends on the order state: a draft or web order accepts everything, a booked or returned order accepts only reference number, assignee, description, invoice heading, pick up location and shipping address, a rented out order adds the due date to that short list, and a completed or void order accepts only reference number, description and invoice heading. Authentication is a single company access token sent as a token header against your own subdomain, and the API is off by default until an account owner enables it. That token carries full read and write rights across orders, customers, business accounts and payments with no per resource scoping, so least privilege is not available and the connection necessarily holds full commercial rights. There are no triggers, because EZRentOut documents no webhook subscription API, so changes are found by polling Get Orders or Filter Rental Items on a schedule. Agents keep the yard, the calendar and the charges in step. The moment equipment leaves is where human-in-the-loop oversight belongs.