> ## 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.

# Assign a physical lock to a unit

> Registers a physical lock assignment to a unit, creating a historical record, note, and unified inbox entry if applicable. If the lock is currently assigned to a different unit, it is unassigned from that unit and reassigned to this one.



## OpenAPI

````yaml /openapi/integration-openapi.json post /api/{portfolio}/portfolios/v1/facilities/{facilityUuid}/units/{unitUuid}/assign-lock
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: 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}/units/{unitUuid}/assign-lock:
    post:
      tags:
        - Physical Locks
      summary: Assign a physical lock to a unit
      description: >-
        Registers a physical lock assignment to a unit, creating a historical
        record, note, and unified inbox entry if applicable. If the lock is
        currently assigned to a different unit, it is unassigned from that unit
        and reassigned to this one.
      operationId: PhysicalUnitLocksController_assignLock
      parameters:
        - name: facilityUuid
          required: true
          in: path
          description: Facility UUID
          schema:
            type: string
        - name: unitUuid
          required: true
          in: path
          description: Unit UUID
          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/AssignLockRequestDto'
      responses:
        '200':
          description: Lock assigned successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AssignLockResponseDto'
        '400':
          description: >-
            Bad Request - Invalid provider, missing provider tag, unit facility
            does not match the specified facility, or an active physical lock
            assignment already exists for this unit and lock ID
        '404':
          description: Unit not found
        '500':
          description: Internal Server Error
components:
  schemas:
    AssignLockRequestDto:
      type: object
      properties:
        lockId:
          type: string
          maxLength: 255
          description: Lock serial number
          example: 86U7U7U2
        lockCode:
          type: string
          maxLength: 32
          description: Lock access code
          example: '5555'
        reason:
          type: string
          enum:
            - Assigned Vacant
            - Overlocked
          description: Reason for lock assignment
          example: Assigned Vacant
      required:
        - lockId
        - lockCode
        - reason
    AssignLockResponseDto:
      type: object
      properties:
        dateCreated:
          format: date-time
          type: string
          description: Date when the lock assignment was created
          example: '2026-01-22T10:30:00.000Z'
        dateUpdated:
          format: date-time
          type: string
          description: Date when the lock assignment was last updated
          example: '2026-01-22T10:30:00.000Z'
        unitUuid:
          type: object
          description: UUID of the unit
          example: 550e8400-e29b-41d4-a716-446655440000
        lockCode:
          type: string
          description: Lock access code
          example: '5555'
      required:
        - dateCreated
        - dateUpdated
        - unitUuid
        - lockCode

````