Choosing the right integration
This page will help you chose the right strategy when integrating with Penneo.
For most modern systems, the Penneo API integration offers the most robust, flexible, and scalable solution for integrating digital signing into your workflows. We recommend the API for almost all use cases that involve cloud, server, or workflow-based automation.
Recommended Path: Penneo API Integration
If your use case involves server-to-server communication, a cloud platform, or automated processes, the Penneo API is the correct choice. This covers the vast majority of modern integrations.
This approach is required for the following scenarios:
- SaaS Vendor (Cloud-Based): Integrating Penneo into your server-based software suite (e.g. ERP, HR, CRM).
- Self-Service Website: Allowing your customers to sign digitally through a self-service platform (e.g., leasing, property administration).
- Automated Business Processes: Integrating digital signing into your internal or external automated workflow management systems (e.g., banks, public sector, accounting).
API Integration Options
Since you will be performing a server-to-server integration, you have two options for implementation:
- Build straight API integration: Write code to interact directly with the REST endpoints. This is the fastest way to access the latest features and functionality.
You can explore and try out API endpoints using our API explorer: https://sandbox.penneo.com/api/docs/ or directly sending a case file documented in our API Reference .
- Use an SDK: Utilize one of our provided Software Development Kits (currently for .NET and PHP) to simplify development. Note that our SDKs lag slightly behind the latest API features.
Reseller note (SaaS Vendors) If you are a SaaS vendor, your end users can either utilize signatures from their own Penneo account, or they can use signatures from your master account, making you a signature reseller. Contact our sales department for information.
Alternative path 1: Desktop Application Integration
If you are a Desktop Application Vendor integrating Penneo into client-side software (e.g., Lawyer or Accounting software), you would most likely integrate via the Penneo Desktop URI-Scheme.
This method allows your users to select documents and recipients in your software and click "Send to Penneo." This action launches the Penneo Desktop app with the data (documents, singers, case file details) pre-filled. Your user can then finalise email content, reminder settings, and other details before sending.
This approach requires that your users have the Penneo Desktop application installed and their own valid Penneo account.
Alternative Path 2: Integration via Print Fields
If your organisation is using an existing, industry-specific piece of software (Software X) that cannot be integrated via the API, you may be able to utilize the Penneo Printer and Print Fields method.
This is often used when:
- You are married to a piece of industry-specific software.
- You need to generate documents and manage contacts without constant copy/pasting.
This method leverages the fact that most software generating documents uses customisable Word templates. By inserting a specific JSON-formatted object (hidden in the PRINT field or in white text on a white background) into your document template, you can pass recipient and other signing information to the Penneo Printer/Desktop App, pre-filling the submission process.
If your third-party software supports customizable Word templates, this solution may work for you.
Updated 16 days ago