SIGNATURUM FOR DEVELOPERS

One API for the full content-protection workflow

Add verifiable deposits, invisible watermarking, managed files, secure embedding, copy monitoring and desktop licensing to your product through one versioned interface.

API documentationManage API keysView plans
Base URLhttps://signaturum.com/api/v1Billing runtime 2.1

From protection to infringement monitoring

The API exposes the same commercial services as the Signaturum dashboard and desktop applications, while keeping permissions, usage and billing centrally controlled.

Digital deposits

Register a SHA-256 fingerprint or upload a file for server-side hashing. Retrieve record status, certificate references and blockchain metadata.

Invisible Watermark V72

Protect images, video and PDF, run detection, monitor asynchronous jobs and download completed protected results.

Managed storage

Upload, list, preview, stream, download and delete files under centrally managed storage, media-duration and PDF-page limits.

Secure embedding

Use stored content in controlled embeds with view, bandwidth, domain, concurrency and branding entitlements.

Crawler monitoring

Create monitored objects, start scans and retrieve jobs, candidates, alerts and supported sources with plan-controlled depth and frequency.

Desktop licensing

Activate and validate desktop application licenses through a dedicated scope without exposing broader account permissions.

Commercial API billing without hidden counters

API access and product consumption are intentionally separate. This lets you price infrastructure load independently from the business value of deposits, watermark jobs, storage or crawler scans.

1. API subscription allowance

Every request uses the active API plan shared by all keys in that subscription: minute, day, month, concurrency and upload-size limits are enforced centrally.

2. Product entitlement

The requested operation must also be available in its product package: deposit.records, watermark.generations, vault.*, embed.* or crawler.*. Read-only calls normally consume only API requests.

Limits enforced by the platform

Values are configured in Billing V2 and may differ by plan or account override. The usage endpoint returns the effective limits and current consumption.

api.requests_minuteRequests allowed in the current minute across the subscription.
api.requests_dayRequests allowed in the current UTC day across the subscription.
api.requests_monthRequests allowed in the active billing period.
api.concurrent_requestsMaximum simultaneous in-flight requests using short leases.
api.max_upload_bytesMaximum accepted body/file size for one upload.

Production and sandbox are separated

The key prefix identifies the environment and prevents test credentials from being mistaken for production credentials.

  • sg_live_… — production key; uses live permissions, usage and product entitlements.
  • sg_test_… — test key; requires sandbox access in the API plan.

Least-privilege scopes

Issue separate keys per application and grant only the actions it needs. Legacy broad scopes remain accepted during migration.

usage:readdeposit:readdeposit:writewatermark:readwatermark:protectwatermark:detectfiles:readfiles:writecrawler:readcrawler:writedesktop:license

Inspect usage before a heavy workflow

GET /usage returns API limits plus product balances, so an integration can postpone work or show a precise upgrade message before starting a large batch.

GET /api/v1/usagecURL
curl https://signaturum.com/api/v1/usage \
  -H "Authorization: Bearer sg_live_YOUR_API_KEY" \
  -H "Accept: application/json"

Ready to integrate Signaturum?

Create a scoped key, test in the sandbox and move the same integration to production when it is ready.

Create an API keyTechnical reference