EZOfficeInventory API
EZOfficeInventory (EZO) is a cloud asset tracking and CMMS platform for managing equipment, inventory, maintenance, and work orders across locations. An unofficial API lets you programmatically pull assets, inventory items, members, locations, work orders, services, and reservations—and push updates like check-outs, check-ins, stock transfers, and maintenance records back into EZOfficeInventory.
What is EZOfficeInventory?
EZOfficeInventory (part of EZO) is a cloud asset tracking and CMMS platform that helps organizations track, manage, and maintain equipment and inventory across locations. Teams use it to track assets with barcode, QR, RFID, and GPS; run check-in/check-out for field operations; automate preventive maintenance and work orders; manage requests and reservations through a self-service portal; and report on utilization to eliminate over-purchasing and surface idle equipment.
Core product areas include:
- Asset Tracking (fixed assets, serialization, GPS/barcode/QR/RFID location tracking)
- Inventory Management (consumables, stock levels, low-stock alerts, transfers between locations)
- Maintenance Management / CMMS (preventive maintenance, work orders, service checklists, technician dispatch)
- Requests & Reservations (self-service portal, availability checking, double-booking prevention)
- Procurement (purchase orders, vendor workflows, bundles and packages)
- Automation & Intelligence (Zoe AI assistant, utilization and catalog optimization reporting)
Common data entities:
- Fixed Assets, Asset Stock, Groups, Subgroups, Bundles
- Inventory Items, Consumables, Stock Levels, Transfers
- Work Orders, Services, Maintenance Records, Checklists
- Members, Roles, Locations, Reservations, Requests
- Purchase Orders, Vendors, Check-out/Check-in Events
The EZOfficeInventory Integration Challenge
EZOfficeInventory exposes a REST API, but turning it into reliable, production-grade automation across a real deployment is non-trivial:
- API access is off by default: companies must explicitly enable the API in Settings and generate an access token before any integration can run
- Token-in-header auth: a single per-account token in the token HTTP header gates every request, with no granular OAuth scopes—rotation and secure storage are on you
- Rate limits: fair-use throttling (roughly 60 requests/minute) returns HTTP 429 with Retry-After, so bulk syncs need careful backoff and pacing
- Subdomain-scoped base URLs: every tenant lives at its own company subdomain, so integrations must be parameterized per account
- Pagination and partial coverage: list endpoints page in small batches (25 by default), and not every screen field or custom attribute is exposed through the API
- Custom fields and configuration drift: asset groups, custom attributes, and workflow rules vary per deployment, so generic integrations break across tenants
- Stateful workflows: check-out, check-in, stock transfers, and work-order state transitions require ordered, idempotent calls to avoid double-bookings and inconsistent inventory
How Supergood Creates EZOfficeInventory APIs
Supergood delivers a resilient, normalized API layer for your EZOfficeInventory account—combining the official REST endpoints with authenticated browser flows where the API stops short, so you integrate once and rely on consistent objects across assets, inventory, maintenance, and people.
- Manages access tokens and per-subdomain endpoints securely, including rotation and credential storage
- Handles rate-limit backoff, 429 retries, and pagination automatically so bulk pulls complete without manual pacing
- Normalizes responses across Assets, Inventory, Work Orders, Members, and Locations so you get consistent objects across every module
- Preserves account-specific groups, custom fields, and workflow rules rather than forcing a generic schema
Use EZOfficeInventory with AI agents: EZOfficeInventory MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules, custom fields, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready EZOfficeInventory adapter tailored to your account configuration and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as EZOfficeInventory evolves.
API Endpoints
Authentication
/authenticateAuthenticate to an EZOfficeInventory account using the company access token (token header) scoped to your subdomain for downstream calls.
Assets
/assetsList fixed assets with filters for group, location, status, and custom fields; paginated results across the account.
Assets
/checkout_assetCheck out an asset to a member or location, or check it back in, updating availability and tracking history.
Inventory
/inventoryRetrieve inventory items and consumables with stock levels, low-stock flags, and per-location quantities.
Inventory
/transfer_stockAdd, sell, or transfer stock quantities of an inventory item between locations.
Maintenance
/work_ordersList work orders and services with status, assignee, asset, and due-date filters for maintenance workflows.
Use Cases
Sync asset and inventory data into your warehouse
- Pull fixed assets, groups, and custom fields into a central warehouse or BI tool - Stream inventory items, stock levels, and low-stock alerts to procurement systems - Reconcile asset and consumable records across locations for unified reporting
Automate check-out and check-in workflows
- Trigger asset check-outs and check-ins from field apps without portal clicks - Validate availability and prevent double-bookings against reservations - Push usage and custody history to downstream operations tools
Drive preventive maintenance and work orders
- Create and update work orders and services from external CMMS triggers - Pull maintenance schedules and checklists for technician dispatch - Surface overdue services and asset downtime to alerting and BI
Keep members, locations, and procurement in sync
- Provision members, roles, and locations from your IdP or HR system - Sync purchase orders and vendor records into finance workflows - Match stock transfers and bundles against location-level inventory
Technical Specifications
Authentication
Per-account access token in the token HTTP header, scoped to your company subdomain, managed in a secure session
Connectivity
Official EZOfficeInventory REST API over HTTPS, augmented by authenticated browser flows where endpoints fall short
Response format
Normalized JSON across Assets, Inventory, Work Orders, Members, and Locations objects
Rate limits
Adaptive throttling tuned to the fair-use limit (~60 requests/minute) with automatic 429 Retry-After handling
Session management
Automatic token rotation, credential vaulting, and per-subdomain endpoint resolution
Data freshness
Near real-time pulls for assets, inventory, and work orders with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for check-out/check-in, stock changes, work-order status, and reservation updates
Latency
Sub-second reads on cached entities; multi-second writes when posting check-outs, transfers, and work orders
Throughput
Horizontally scaled workers with pagination handling sized to multi-location asset and inventory volume
Reliability
Retry, backoff, and idempotency keys for check-outs, stock transfers, and work-order transitions
Adaptation
Continuous monitoring of EZOfficeInventory API releases and account-specific configuration drift
Frequently asked questions
Yes. EZOfficeInventory ships with the API disabled by default. An admin enables it in Settings and generates an access token; Supergood then manages that token securely, including rotation, so you don't have to embed it in your own systems.
The API enforces a fair-use limit of roughly 60 requests per minute and returns HTTP 429 with a Retry-After header when exceeded. Supergood paces requests, backs off automatically, and resumes paginated pulls so large syncs complete without manual throttling.
Yes. Supergood normalizes both fixed assets (assets.api) and inventory/consumables (inventory.api), along with work orders, services, members, locations, reservations, and purchase orders, so you integrate every module through one consistent surface.
Yes. Stateful actions like check-out, check-in, and stock transfers are exposed as ordered, idempotent calls with retry handling, so availability and inventory stay consistent and double-bookings are avoided.
Each account is profiled against its configured groups, custom attributes, and workflow rules. Supergood preserves account-specific fields and states rather than forcing a generic schema, so integrations don't break across deployments.