Visual PDF field placement
Render document pages and position signature, initials, date, text and checkbox fields precisely.
Product
Electronic PDF signature
Configure signers, fields, authentication and evidence for traceable PDF signing processes.
Overview
Configure signers, fields, authentication and evidence for traceable PDF signing processes.
Real interface
An environment integrated into Apification
The screenshot shows the product’s current interface inside an Apification account.
Visual PDF field placement
Render document pages and position signature, initials, date, text and checkbox fields precisely.
Multiple signers
Create identified signers and assign every required field to the person responsible for completing it.
Sequential or parallel flow
Choose whether all signers can act at once or must complete the document in a defined order.
Features
What Electronic PDF signature can do
Multiple signers
Create identified signers and assign every required field to the person responsible for completing it.
Sequential or parallel flow
Choose whether all signers can act at once or must complete the document in a defined order.
Secure access methods
Use individual links, OTP or supported external authentication according to the process requirements.
Required fields and validation
Prevent completion while mandatory signatures or data remain empty or invalid.
Expiry and reminders
Limit access to a defined period and notify pending signers without manual follow-up.
Evidence and audit trail
Record relevant identities, timestamps, events and technical evidence for each signing process.
Signed document result
Generate the completed PDF and retain the request, status and evidence inside Cloud.
Webhook tracking
Notify connected systems about delivery, access, signature, completion or failure events.
Technical information
Inputs, results, and work continuity
Supported inputs
PDF, signers, roles, fields, order, and authentication methods.
Results and export
Signature links, completed document, statuses, tracking, and evidence.
Work continuity
The request retains signers, events, and deliverables without altering the sent PDF.
Practical examples
From input to result
Configuration
Multiple signers
- Result
- Create identified signers and assign every required field to the person responsible for completing it.
Configuration
Sequential or parallel flow
- Result
- Choose whether all signers can act at once or must complete the document in a defined order.
Configuration
Secure access methods
- Result
- Use individual links, OTP or supported external authentication according to the process requirements.
Recommended configurations
Sequential signingParallel signingOTP accessExternal auth
Limits and requirements
- The signature flow uses a stable PDF as its source document.
- OTP and notifications require a working email configuration.
- Legal effect depends on the identification method and applicable legal requirements.
Privacy and data
- Signer data, links, and OTP are limited to the corresponding signature process.
- Changing a sent document breaks its correspondence and requires a new request.
- Statuses, events, and technical evidence are retained for traceability.
Integration and automation
- Public links and published views distribute the result.
- Webhooks report relevant changes and retain deliveries, responses, and retries.
- The API creates, reads, and manages Cloud resources with account credentials.
Plans and usage
- Originals, projects, versions, and results use account storage.
- Public views and completed signatures use the configured signature tariffs.
Frequently asked questions
Questions about Electronic PDF signature
No. Their legal level depends on the identification method, provider, and regulations applicable to the specific process.
You should not. Changing the document breaks its correspondence with what was presented to signers and requires a new request.
Each signer uses their link and, depending on configuration, may need OTP or external authentication before completing their fields.