openapi: 3.0.3 info: title: EZRentOut Assets Locations API description: 'REST API for EZRentOut, the cloud equipment rental management platform from EZO (the company behind EZOfficeInventory). The API lets paying customers build custom integrations against their own rental account: orders (baskets), fixed assets, inventory and stock assets, bundles, customers and businesses, members, locations, availability, order payments and taxes, purchase orders, and maintenance / work orders. Every request is scoped to the customer''s own tenant at https://{subdomain}.ezrentout.com and is authenticated with a per-company access token. The token is generated in Settings (API is disabled by default and must be enabled by the account owner) and sent in a `token` HTTP header over HTTPS. Resource endpoints are namespaced with a `.api` suffix. List endpoints are paginated with a `page` query parameter (default 1). Dates use `mm/dd/yyyy` and times use `hh:mm`. Endpoint paths and the authentication model are grounded in EZRentOut''s public developer documentation (https://ezo.io/ezrentout/developers/). Request and response schemas here are modeled representations - EZRentOut does not publish a machine-readable OpenAPI document, so property sets are illustrative rather than exhaustive.' version: '1.0' contact: name: EZO / EZRentOut Support url: https://ezo.io/ezrentout/developers/ email: support@ezo.io termsOfService: https://ezo.io/ezrentout/terms-of-service/ servers: - url: https://{subdomain}.ezrentout.com description: Customer rental account (tenant) variables: subdomain: default: your-company description: Your EZRentOut company subdomain. security: - tokenAuth: [] tags: - name: Locations description: Warehouses / branches that hold assets and inventory. paths: /locations.api: get: operationId: listLocations tags: - Locations summary: List locations parameters: - $ref: '#/components/parameters/Page' responses: '200': description: A page of locations. content: application/json: schema: type: object properties: locations: type: array items: $ref: '#/components/schemas/Location' post: operationId: createLocation tags: - Locations summary: Create a location requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/Location' responses: '201': description: The created location. content: application/json: schema: $ref: '#/components/schemas/Location' /locations/{locationId}.api: get: operationId: getLocation tags: - Locations summary: Get location details parameters: - $ref: '#/components/parameters/LocationId' responses: '200': description: The location. content: application/json: schema: $ref: '#/components/schemas/Location' patch: operationId: updateLocation tags: - Locations summary: Update a location parameters: - $ref: '#/components/parameters/LocationId' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/Location' responses: '200': description: The updated location. content: application/json: schema: $ref: '#/components/schemas/Location' components: schemas: Location: type: object properties: id: type: integer name: type: string street: type: string active: type: boolean parameters: Page: name: page in: query description: Page number for paginated list results (default 1). schema: type: integer default: 1 LocationId: name: locationId in: path required: true description: The location ID. schema: type: integer securitySchemes: tokenAuth: type: apiKey in: header name: token description: Per-company access token generated in Settings (API must be enabled by the account owner). Sent in the `token` HTTP header on every request over HTTPS.