Choose your XCIM integration path

Collect permission for your own product, or validate a client list as an email service provider.

Company: your sites and consent

Start here if your organization operates the website or application where a person chooses what emails to receive. One Company can manage several sites. Each integration needs a clearly defined sender and purpose.

Company guide: site to first receipt →

ESP: your clients and their lists

Start here if you send email or evaluate lists for another company. The client gives your ESP access to a specific application and purpose; a provider code alone is not permission.

ESP guide: access to CSV results →

If you do both

Keep the roles separate. Collect consent for your own product in the Company area; evaluate authorized client lists in the ESP area. Do not reuse permission across unrelated senders, tenants, applications or communication types.

See a verified example

Deploy to Agents: receipt after backend restart and two-row ESP evaluation. This is an operator-managed implementation result. Its matching row had active Emabled permission but no available public proof.

Protocol and product

These guides describe the responsibilities of each role. XCIM implementation roles are vendor-neutral. Emabled’s first-receipt guide supplies the product-specific setup. Emabled is one implementation, not a mandatory XCIM trust root.

Latest specification · draft-saez-xcim-04

Experimental individual Internet-Draft. A bounded C01/SR01 testnet pilot verified consent reuse and revocation on 26 October 2026; production readiness remains open.