GigaSignature Documentation

Introduction

Welcome to the GigaSignature documentation, your eIDAS-compliant electronic signature solution. This documentation will guide you through all the features of our platform, from quick start to advanced API integrations.

Whether you're a beginner or an experienced user, this documentation contains all the information you need to get the most out of GigaSignature.

Getting Started

GigaSignature simplifies the electronic signature process in 3 simple steps:

  1. Upload your PDF document
  2. Configure signature areas and invite signers
  3. Sign and receive the certified document

πŸ’‘ Tip: You can create a free account to test all features without commitment.

Create Account

To start using GigaSignature, you need to create an account:

Registration Steps

  1. Access the registration page

    Click "Create Account" from the homepage

  2. Fill out the form
    • Full name
    • Professional email address
    • Secure password (min. 8 characters)
    • Organization name
  3. Verify your email

    A confirmation email will be sent to you

  4. Configure your profile

    Add billing information if necessary

Note: Two-factor authentication (2FA) is recommended to secure your account.

Upload Document

Accepted Formats

GigaSignature only accepts PDF documents to ensure integrity and compatibility.

How to Upload

  1. Log in to your dashboard
  2. Click "New Signature Process"
  3. Drag and drop your PDF or click to browse
  4. Wait for the upload to complete

Limitations:

  • Maximum size: 10 MB per file
  • Password-protected documents not supported
  • Interactive PDF forms will be flattened

Configure Signature

Signature Areas

Use our visual editor to place signature areas:

  • Drag and drop: Position areas where you want
  • Resize: Adjust size as needed
  • Assign: Allocate each area to a signer
  • Order: Define signing order if necessary

Signature Options

Sequential Signature

Signers sign in defined order

Parallel Signature

All signers can sign simultaneously

Security Settings

  • Mandatory OTP: Require code verification
  • OTP Method: Email, SMS, or signer's choice
  • Expiration Date: Time limit for signing

Invite Signers

Add Signers

For each signer, you must provide:

  • Full name: For identification
  • Email: To receive invitation
  • Phone (optional): For SMS OTP
  • Custom message: Specific instructions

Types of Signers

External Signer

Person outside your organization

Internal User

Member of your GigaSignature team

Sign Document

Signing Process

  1. Receive invitation

    Signer receives email with secure link

  2. Verify identity

    Enter OTP code received by email or SMS

  3. Review document

    Read all pages of the document

  4. Apply signature

    Click "Sign" to validate

  5. Download certificate

    Receive signed document and certificate

Security: Each signature is timestamped and cryptographically sealed to ensure its integrity.

Track Status

Possible States

Pending Document awaiting signatures
In Progress Signatures being collected
Completed All signatures collected
Expired Signing deadline exceeded

Notifications

You receive notifications for:

  • Each signature applied
  • Signature refusals
  • Process completion
  • Automatic reminders

Download Certificate

Available Documents

Once the process is complete, you can download:

  • Signed document: PDF with all signatures
  • Signature certificate: Legal proof of process
  • Audit trail: Detailed log of actions

Certificate Content

  • Signer identity
  • Timestamp of each signature
  • SHA-256 document fingerprint
  • Authentication method used
  • IP address and location

API Integration

Getting Started with API

GigaSignature offers a complete RESTful API to integrate electronic signature into your applications.

Authentication

Use your API key in the Authorization header:

Authorization: Bearer sk_live_YOUR_API_KEY

Complete Example: Create a Signature Process

Here's a complete example to create and send a signature process:

1️⃣ Upload Your Documents

curl -X POST https://api.giga-signature.com/api/v1/documents \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Accept: application/json" \
  -F "file=@contract.pdf" \
  -F "name=Service Contract 2025"

Response:

{
  "data": {
    "id": "doc_abc123",
    "name": "Service Contract 2025",
    "pages": 5
  }
}

2️⃣ Create a Signature Process

curl -X POST https://api.giga-signature.com/api/v1/signature-processes \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Client ABC Contract",
    "description": "Annual service contract",
    "sequential_signing": false,
    "require_otp": true,
    "otp_method": "choice",
    "documents": [
      {
        "document_id": "doc_abc123",
        "order": 1
      }
    ],
    "signers": [
      {
        "name": "John Smith",
        "email": "john.smith@example.com",
        "phone": "+14155552671",
        "language": "en"
      },
      {
        "name": "Jane Doe",
        "email": "jane.doe@example.com",
        "language": "en"
      }
    ]
  }'

3️⃣ Place Signature Fields

curl -X POST https://api.giga-signature.com/api/v1/signature-processes/proc_7h8i9j0k/fields \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fields": [
      {
        "document_id": "doc_abc123",
        "signature_id": "sig_1a2b3c4d",
        "type": "signature",
        "label": "Client Signature",
        "page": 5,
        "position_x": 15,
        "position_y": 70,
        "width": 25,
        "height": 10
      },
      {
        "document_id": "doc_abc123",
        "signature_id": "sig_2b3c4d5e",
        "type": "signature",
        "label": "Partner Signature",
        "page": 5,
        "position_x": 50,
        "position_y": 70,
        "width": 25,
        "height": 10
      }
    ]
  }'

4️⃣ Send to Signers

curl -X POST https://api.giga-signature.com/api/v1/signature-processes/proc_7h8i9j0k/send \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY"

Digital Vault

Access signed documents stored securely:

πŸ“‚ List Vault Documents

curl -X GET "https://api.giga-signature.com/api/v1/vault/documents?status=active&tags=contract,2025" \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY"

Available parameters:

  • search - Search in names and tags
  • status - active, archived, expiring, expired
  • date_from / date_to - Date filtering
  • tags - Filter by tags (comma separated)

πŸ“¦ Download Complete Package

curl -X GET "https://api.giga-signature.com/api/v1/vault/documents/123/package" \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -o "document-package.zip"

The ZIP package contains the signed document, certificate, and audit trail.

Webhooks

Configure webhooks to receive real-time notifications:

πŸ”” Configure a Webhook

curl -X POST https://api.giga-signature.com/api/v1/webhooks \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://your-app.com/webhooks/signature",
    "events": [
      "signature.completed",
      "signature.refused",
      "process.completed"
    ],
    "active": true
  }'

πŸ” Verify HMAC Signature

PHP Example:

$payload = file_get_contents('php://input');
$signature = 'sha256=' . hash_hmac('sha256', $payload, $webhook_secret);
$is_valid = hash_equals($signature, $_SERVER['HTTP_X_SIGNATURE']);

Node.js Example:

const crypto = require('crypto');
const signature = 'sha256=' + crypto
  .createHmac('sha256', webhookSecret)
  .update(payload)
  .digest('hex');
const isValid = signature === req.headers['x-signature'];

Archives

Access archived processes after 90 days:

πŸ—„οΈ Download an Archive

curl -X GET https://api.giga-signature.com/api/v1/archives/123/download \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -o "archive-process-123.zip"

Error Handling

The API returns structured error messages:

{
  "error": {
    "code": "validation_error",
    "message": "The provided data is invalid",
    "errors": {
      "signers.0.email": ["The email address is invalid"],
      "file": ["The file must be a PDF"]
    }
  }
}

Available SDKs

PHP

composer require giga-signature/php-sdk

Node.js

npm install @giga-signature/sdk

Python

pip install giga-signature

πŸ“š Complete documentation: Check our interactive API documentation with all endpoints, parameters, and examples.

Security

Security Measures

GigaSignature implements best security practices:

πŸ” Encryption

  • TLS 1.3 for communications
  • AES-256 for storage
  • RSA-2048 for signatures

πŸ›‘οΈ Protection

  • 2FA authentication
  • Intrusion detection
  • Redundant backup

Compliance

  • eIDAS: European regulation on electronic identification
  • GDPR: Personal data protection
  • ISO 27001: Information security management

Frequently Asked Questions

Can I sign from my mobile?

Yes, GigaSignature is fully responsive and works on all devices.

How long are documents stored?

Signed documents are stored for a minimum of 10 years, in compliance with legal requirements.

Can I cancel a signature process?

Yes, as long as all signatures have not been collected, you can cancel the process.

Are signatures legally valid?

Yes, our advanced electronic signatures are legally recognized throughout the EU under the eIDAS regulation.

Support

Need Help?

Our team is here to assist you:

πŸ“§

Email

support@gigasignature.com

πŸ’¬

Chat

Available online

πŸ“š

Knowledge Base

Articles and tutorials

Support Hours: Monday - Friday, 9 AM - 6 PM CET