> ## 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 journal entries by UUIDs for a facility > Retrieves each journal entry with its debit and credit lines: the GL account posted to, the accounting basis, the amount in pennies, and the pointers back to the unit rental record, invoice, invoice item and payment that produced the line. ## OpenAPI ````yaml /openapi/integration-openapi.json post /api/{portfolio}/portfolios/v1/facilities/{facilityUuid}/journalEntries/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: 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 paths: /api/{portfolio}/portfolios/v1/facilities/{facilityUuid}/journalEntries/get_by_uuids: post: tags: - Journal Entries summary: Get journal entries by UUIDs for a facility description: >- Retrieves each journal entry with its debit and credit lines: the GL account posted to, the accounting basis, the amount in pennies, and the pointers back to the unit rental record, invoice, invoice item and payment that produced the line. operationId: PrivateApiJournalEntriesController_getJournalEntriesByUuids 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/GetJournalEntriesByUuidsDto' responses: '200': description: Successfully retrieved journal entry data content: application/json: schema: type: array items: $ref: '#/components/schemas/JournalEntryResponseDto' components: schemas: GetJournalEntriesByUuidsDto: type: object properties: journalEntryUuids: example: - 8f1c2d3e-4a5b-6c7d-8e9f-0a1b2c3d4e5f - b2c3d4e5-6f7a-8b9c-0d1e-2f3a4b5c6d7e description: Array of journal entry UUIDs to retrieve data for type: array items: type: string format: uuid required: - journalEntryUuids JournalEntryResponseDto: type: object properties: journalEntryUuid: type: string format: uuid example: 8f1c2d3e-4a5b-6c7d-8e9f-0a1b2c3d4e5f description: UUID of the journal entry. description: type: string nullable: true example: Rent billing - June description: >- Narrative recorded with the journal entry, naming the operation that produced it. createdAt: format: date-time type: string example: '2026-06-01T06:00:12.000Z' description: When the journal entry was posted. updatedAt: format: date-time type: string example: '2026-06-01T06:00:12.000Z' description: >- When the journal entry was last modified. Nothing amends a posted journal entry — a correction is posted as a new entry of the opposite sign — so in practice this equals createdAt. transactions: description: >- Debit and credit lines composing the entry. The debits sum to the credits. type: array items: $ref: '#/components/schemas/TransactionEntryResponseDto' required: - journalEntryUuid - description - createdAt - updatedAt - transactions TransactionEntryResponseDto: type: object properties: transactionEntryUuid: type: string format: uuid example: 11aa22bb-33cc-44dd-55ee-66ff77aa88bb description: UUID of the transaction entry — one debit or credit line. glAccount: description: GL account this line posts to. allOf: - $ref: '#/components/schemas/JournalEntryGlAccountDto' accountingBasis: $ref: '#/components/schemas/AccountingBasis' example: ACCRUAL debitAmountInPennies: type: number example: 13531 description: >- Debit side of the line, in pennies. Exactly one of debitAmountInPennies and creditAmountInPennies is greater than zero; the other is 0. creditAmountInPennies: type: number example: 0 description: >- Credit side of the line, in pennies. Within a journal entry, the debits sum to the credits. facilityUuid: type: string format: uuid example: aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee description: >- UUID of the facility the line belongs to. GL accounts are held by the organization behind the facility, and each organization has exactly one facility, so this echoes the facility in the request path — it resolves every line, including merchandise, reservation and auction lines that carry no rental record. unitRentalRecordUuid: type: string nullable: true format: uuid example: 7d8e9f0a-1b2c-3d4e-5f6a-7b8c9d0e1f2a description: >- UUID of the unit rental record the line originated from. Null on lines with no tenancy behind them, such as merchandise sales, reservations and auction postings. invoiceUuid: type: string nullable: true format: uuid example: 4e5f6a7b-8c9d-0e1f-2a3b-4c5d6e7f8a9b description: >- UUID of the invoice the line originated from. Null when the posting has no invoice behind it. invoiceItemUuid: type: string nullable: true format: uuid example: 9c0d1e2f-3a4b-5c6d-7e8f-9a0b1c2d3e4f description: >- UUID of the invoice item the line originated from. Null on the receivable leg of a billing, which answers to the invoice as a whole rather than to one of its items. paymentUuid: type: string nullable: true format: uuid example: 0e1f2a3b-4c5d-6e7f-8a9b-0c1d2e3f4a5b description: >- UUID of the payment the line originated from. Null on lines that are not driven by a payment. intacctJournalSymbol: type: string nullable: true example: null description: >- Reserved, always null. Monument has no journal-symbol concept of its own; derive it from the GL account category and the source pointers on the line. required: - transactionEntryUuid - glAccount - accountingBasis - debitAmountInPennies - creditAmountInPennies - facilityUuid - unitRentalRecordUuid - invoiceUuid - invoiceItemUuid - paymentUuid - intacctJournalSymbol JournalEntryGlAccountDto: type: object properties: glAccountUuid: type: string format: uuid example: c1d2e3f4-a5b6-47c8-9d0e-1f2a3b4c5d6e description: >- UUID of the GL account the line posts to. It is the same identifier the facility chart-of-accounts route reports. glCode: type: string nullable: true example: '11000' description: >- GL code of the account, as entered by the operator in Settings. Null until they enter one; it is the field to map against an external chart of accounts. accountName: type: string example: Accounts Receivable description: >- Name of the GL account. The accrual and cash accounts of the same item usually share this name, so read accountingBasis to tell them apart. accountCategory: $ref: '#/components/schemas/GlAccountCategory' example: Asset accountingBasis: $ref: '#/components/schemas/AccountingBasis' example: ACCRUAL required: - glAccountUuid - glCode - accountName - accountCategory - accountingBasis AccountingBasis: type: string description: >- Accounting basis the account belongs to. ACCRUAL recognises the amount when the invoice is issued, CASH when the money is received. enum: - ACCRUAL - CASH GlAccountCategory: type: string description: >- Chart-of-accounts category the account falls under, which decides whether it is debited or credited by a movement. enum: - Asset - Liability - Revenue - Expense - Equity - Contra-Revenue - Contra-Liability ````