Lock PDF API for Developers

    Feature

    Use the sandbox below to test lock/encryption quickly. Detailed notes are at the bottom of this page.

    Use cases

    Why lock

    • Secure sharing with partners
    • Protect HR / legal documents
    • Encrypt KYC packets before sending
    • Control access via password
    Prefer the full playground? Use Try Now.

    Parameters

    What you send

    url
    required

    PDF URL to lock.

    password
    required

    User password (required to open).

    owner_password
    optional

    Owner password (to change permissions). Defaults to user password.

    input_password
    optional

    If the PDF is already password protected.

    encryption
    optional

    aes256 (default), aes128, or rc4.

    permissions
    optional

    Object: print, copy, modify, annotate, fill_forms, extract, assemble. All default true.

    output
    optional

    url, file, or base64.

    output_name
    optional

    Filename for downloads.

    Sandbox

    Lock a PDF from URL

    Result

    Preview, response, and cURL command

    Description

    Implementation notes and workflow guidance

    Password-protect PDFs for secure sharing and compliant handling.

    Add encryption as a standard step before sending invoices, statements, or contracts. Use dynamic passwords per recipient and preserve a clear audit trail for access control and policy-driven document workflows.

    In production, pair lock operations with deterministic naming, delivery confirmation, and retry-safe processing. That pattern makes it easier to prove document handling policy compliance while maintaining predictable automation behavior across internal systems and external recipients.

    Teams often combine lock actions with role-based routing so only intended recipients can open documents. This approach improves security posture while keeping customer-facing delivery flows efficient and automated.