Loyva Developer Documentation

Build with Loyva

Electronic signing, secure document vaulting, and UCC §9-105 compliance — integrate in minutes with our REST API.

What is Loyva?

Loyva is a B2B platform that provides:

• Electronic Signing (E-Sign) — Send documents for legally binding e-signatures
• Electronic Vault (E-Vault) — Tamper-evident storage for signed documents with SHA-256 integrity verification and weekly re-verification
• UCC §9-105 Compliance — Automated compliance engine that evaluates all 8 requirements for electronic chattel paper

How integration works

Partners integrate with Loyva through two channels today:

Channel	Use case	Auth
REST API	Create envelopes, manage customers, check compliance	API key (X-API-Key header)
Webhooks	Get notified when envelopes are signed, vaulted, or transferred	HMAC-SHA256 signature verification

A drop-in Embed SDK for rendering the sign and vault widgets in your own app is in progress — contact your Loyva point of contact if you need embedded signing in the near term.

Quick links

Quickstart

Create your first envelope and send it for signature in under 5 minutes.

API Reference

Complete REST API documentation with request/response examples.

Partner Integration

API key management, scopes, and partner-specific endpoints.

Webhooks

Real-time notifications for envelope and vault events.

UCC Compliance

Understand the 8-check compliance engine for electronic chattel paper.

Base URLs

Environment	Base URL
Staging	https://api.stg.loyva.net/api/v2
Production	https://api.loyva.net/api/v2

All API requests use HTTPS. HTTP requests are rejected.

Platform status

Item	Status
Current availability	Private beta — staging environment
GA target	Q3 2026
Uptime SLA (GA)	99.9% monthly, defined in the enterprise agreement
SOC 2 Type II	Audit in progress — report available under NDA on request

Contact your Loyva point of contact for the latest GA timeline or to request the SOC 2 attestation letter.

Response envelope

All successful API responses wrap the payload in a top-level data field. Paginated responses additionally include a meta object.

{ "data": { /* resource */ } }
{ "data": [ /* resources */ ], "meta": { "page": 1, "limit": 20, "total": 85 } }

Errors are returned as { "error": "...", "details"?: [...] } with the appropriate HTTP status code (see Errors).