Changelog

1.0.0-target — November 2026

First documentation Preview of the target contract.

• POST /api/integrations/v1/licensing-requests — submit approved single-product order data and receive a Buyer onboarding link. Idempotency keys, duplicate-order handling, decimal amounts and UTC validity periods.
• POST /api/integrations/v1/licenses/verify — fail-closed verification of the canonical licenceKey, with Seller-scoped product, Buyer/rights-holder organization references and seat allowance (the Seller still enforces user access and seats).
• Webhook events onboarding.completed and licence.issued, authenticated by their own webhookSignature scheme (LC-Signature HMAC-SHA256 over <LC-Timestamp>.<raw body>), not by the Seller API key.
• licence.issued carries the canonical licenceKey, initial status, validity period, seat allowance, Seller/product/Buyer/license-holder IDs, accepted terms version and links to the licensing request and onboarding acceptance.
• One licensing request issues one corporate license; optional quantity is the seat or unit allowance within it.
• RFC 9457 problem details with stable error codes.
• Guidance for MCP servers and agent tools.
• Agent-readable resources: llms.txt, Markdown guides and openapi-target.json.

Not in this version

• Multiple products or PO line items in one licensing request (expected to be added without breaking single-product requests).
• One license per seat.
• Licensing-request status lookup for reconciliation by requestId or externalOrderId.
• Delivery of onboarding links by LicenChain.