SecurePDF Encryptor API Documentation

The SecurePDF Encryptor API allows users to upload a PDF file and receive an encrypted version in response. The API secures the document using AES-128 encryption and supports both user and owner passwords for enhanced protection.

Key Features

  • AES-128 Encryption: Ensures secure file encryption with industry-standard security.
  • User and Owner Passwords: Supports dual-password protection for enhanced control.
  • Fast & Secure Processing: Quickly encrypts PDFs while maintaining data integrity.
  • Cloud Storage Integration: Securely stores encrypted files with unique download links.
  • RESTful API: Simple and intuitive API endpoints for seamless integration.

Getting Started

To start using the SecurePDF Encryptor API, follow these steps:

  • Sign Up: Register for an API key to access the service.
  • Authenticate Requests: Use your API key in the headers to authenticate API calls.
  • Upload a PDF: Send a PDF file for encryption using the designated API endpoint.
  • Receive Encrypted File: Get a secure download link for the encrypted PDF.

Authentication

All requests require an API key, passed in the headers as follows:

{ "x-api-key": "YOUR_API_KEY", "x-app-username": "YOUR-API_USERNAME" }

Note: Keep your API key secure and do not share it publicly.

API Endpoints

The main endpoint for encrypting PDFs:

{ "POST": "/file/encrypt-pdf" }

Request Parameters:

  • filepart: The PDF file to encrypt (required).
  • password: A strong password for encryption (required).

Response Example:

{
    "msg": "Your file was encrypted successfully. Use the link below to download the PDF.",
    "status": 200,
    "data": "https://assets.cysecinnovation.com/encrypted_example.pdf"
  }

Rate Limits

To ensure fair usage, API requests are limited:

  • 50 requests per minute: Exceeding this limit results in a 429 Too Many Requests response.

For higher limits, contact our support team.

Error Handling

The API uses standard HTTP status codes for error handling:

{
    "status": 400,
    "error": "Bad Request",
    "message": "Wrong x-api-key and/or x-app-username"
  }
{
    "status": 400,
    "error": "Bad Request",
    "message": "Insufficient balance for live API request."
  }

Debugging Tips:

  • Ensure your API key is valid and included in the request headers.
  • Check that the uploaded file meets the format and size requirements.
  • Monitor rate limits to avoid request rejections.

© 2025 cysecinnovation All rights reserved