> ## Documentation Index > Fetch the complete documentation index at: https://api.monument.io/llms.txt > Use this file to discover all available pages before exploring further. # Get facility rent changes by UUIDs > Retrieves rent change details for the provided array of UUIDs within a specific facility, most recent rent period first. Each row carries the rent that applied immediately before it on the same tenancy, resolved from the tenancy full history rather than from the requested batch. ## OpenAPI ````yaml /openapi/integration-openapi.json post /api/{portfolio}/portfolios/v1/facilities/{facilityUuid}/rentChanges/get_by_uuids openapi: 3.0.0 info: title: Monument Integration API description: Monument Integration API version: '1.0' contact: {} servers: - url: https://public-api.prd.monument.io description: Production - url: https://public-api.stg.monument.io description: Staging security: [] tags: - name: Portfolios description: List portfolios accessible to the API key - name: Facilities description: Facility retrieval and coverage-option configuration - name: Units description: Unit listing and MORA execution - name: Unit Groups description: Unit group listing, rate management, and unit assignment - name: Rental Records description: Rental record listing, coverage, fees, autopay, and payment links - name: Ledger Entries description: Ledger entry retrieval at facility and rental-record level - name: Rent Changes description: >- Applied rent-change history per tenancy, with the rent that preceded each period - name: Leads description: Lead listing and lease sending - name: Tasks description: Task creation and listing for integrations - name: Tenants description: Tenant listing and person updates - name: People description: Person listing - name: Notes description: Note listing and creation for tenants and leads - name: Auctions description: Auction listing - name: Coverage description: Portfolio-level coverage CRUD and coverage history - name: Summary description: Portfolio-level aggregate summaries (insurance enrollment/occupancy) - name: Promotions description: Promotion listing - name: ECRI description: Effective Current Rent Increase scheduling - name: Item Types description: Item type listing per facility - name: GL Accounts description: Chart of accounts listing per facility - name: Journal Entries description: GL journal entry feed per facility, line by line - name: Delinquencies description: Delinquency listing per facility - name: Physical Locks description: Physical lock assignment and unassignment - name: Lead Source Options description: Lead source option listing - name: Webhooks description: Webhook subscription management - name: Payments description: Payment profile creation and removal paths: /api/{portfolio}/portfolios/v1/facilities/{facilityUuid}/rentChanges/get_by_uuids: post: tags: - Rent Changes summary: Get facility rent changes by UUIDs description: >- Retrieves rent change details for the provided array of UUIDs within a specific facility, most recent rent period first. Each row carries the rent that applied immediately before it on the same tenancy, resolved from the tenancy full history rather than from the requested batch. operationId: PrivateApiRentChangesController_getFacilityRentChangesByUuids parameters: - name: facilityUuid required: true in: path schema: type: string - in: path required: true name: portfolio schema: example: abc_selfstorage - in: header required: true name: x-api-key schema: example: monument-2230012-2312321 description: >- Api key required to authenticate your request. Please reach out to monument for a key. requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/GetRentChangesByUuidsRequestDto' responses: '200': description: Rent change details retrieved successfully content: application/json: schema: type: array items: $ref: '#/components/schemas/RentChangeDetailsResponseDto' '400': description: Bad Request (e.g., Too many uuids, invalid input) components: schemas: GetRentChangesByUuidsRequestDto: type: object properties: rentChangeUuids: example: - 7a3d88e1-2f10-11f0-9c3a-0242ac120002 - 9c1f0a52-4b7e-11f0-9c3a-0242ac120002 description: Array of rent change UUIDs to retrieve data for type: array items: type: string format: uuid required: - rentChangeUuids RentChangeDetailsResponseDto: type: object properties: unitHistoricalRentUuid: type: string format: uuid example: 9c1f0a52-4b7e-11f0-9c3a-0242ac120002 description: UUID of the rent change record unitRentalRecordUuid: type: string format: uuid example: 1d9b40c7-0a55-11f0-9c3a-0242ac120002 description: UUID of the tenancy this rent applied to unitUuid: type: string format: uuid example: b2e7c318-0a55-11f0-9c3a-0242ac120002 description: UUID of the unit unitGroupUuid: type: string nullable: true format: uuid example: e5f1a904-0a55-11f0-9c3a-0242ac120002 description: UUID of the unit group startDate: type: string format: date example: '2025-09-01' description: >- Date this rent took effect. A tenancy that reached move-out with no rent history recorded carries a synthetic row dated 1971 holding the unit rate rather than a rent that was ever charged. endDate: type: string nullable: true format: date example: '2026-02-01' description: >- Date this rent stopped applying. Null while it is the latest rent on the tenancy. Written when a period is closed — at move-out, and when a scheduled rent increase is applied — so a non-null value on its own is NOT a move-out signal. On a tenancy with several rent periods the move-out date may land on a row other than the last one. rentInPennies: type: number example: 19500 description: Rent charged from startDate, in pennies priorRentInPennies: type: number nullable: true example: 18000 description: >- Rent that applied immediately before this one on the same tenancy, in pennies. Null on the tenancy first rent record. priorRentStartDate: type: string nullable: true format: date example: '2025-03-01' description: >- Date the prior rent took effect. Null on the tenancy first rent record. priorRentEndDate: type: string nullable: true format: date example: '2025-08-31' description: >- Date the prior rent stopped applying. Null on the tenancy first rent record, and also whenever that earlier period was never closed — a rent change applied outside move-out and outside scheduled-increase processing leaves it empty, so this field is commonly absent even when a prior rent exists. rentChangeReason: type: string enum: - ECRI - MOVE_IN - MANUAL_ADJUSTMENT_MORA - AUTOMATED_ECRI example: ECRI description: >- Why the rent changed. MOVE_IN is also the column default, so a legacy row saved without an explicit reason reports MOVE_IN. AUTOMATED_ECRI is an existing-customer rate increase applied by auto-scheduling, and is NOT returned by a rentChangeReason=ECRI filter. isIncrease: type: boolean example: true description: Whether this change raised the rent rentChangeScheduledDate: type: string nullable: true format: date example: '2025-08-02' description: >- Date the change was scheduled on, when it was scheduled ahead of time. Null otherwise. required: - unitHistoricalRentUuid - unitRentalRecordUuid - unitUuid - unitGroupUuid - startDate - endDate - rentInPennies - priorRentInPennies - priorRentStartDate - priorRentEndDate - rentChangeReason - isIncrease - rentChangeScheduledDate ````