Overview

The Developer API gives customer systems one integration surface for qualified-signature workflows, connected-device orchestration, diagnostics, webhooks, and tenant administration.

Instead of building separate integrations for local signing, device state, XML signing, webhook delivery, and operational logs, your backend integrates with one API layer and the platform routes each request to the correct execution path.

What you can build

  • Submit XML documents for qualified signing.
  • Execute tunneled local requests through a connected desktop environment.
  • List connected devices and inspect device metadata.
  • Trigger diagnostics and retrieve support logs.
  • Configure webhook subscriptions for operational events.
  • Manage tenant configuration and API keys.

Integration model

  1. Your backend sends a request to the API.
  2. The request is authenticated with X-API-Key.
  3. The API resolves the tenant and target execution path.
  4. A connected desktop client or service-side path performs the operation.
  5. The API returns a normalized response.
  6. Webhooks notify your system about asynchronous operational events.

Main areas

  • Signing
  • Devices
  • Webhooks
  • Tenant administration
  • Health checks
  • Debug and diagnostics