ESP guide: from client access to CSV results
Choose the authorized client site, validate its list and understand each permission result.
For a provider evaluating a company’s list. Your client operates the product where people consent. You operate the ESP workspace. You do not need to add the client’s website as your own Company application.
1. Share your provider code and receive access
In Emabled, sign in to the ESP area and complete the workspace/security setup. Copy Your provider code and send it to your client. Ask the client to use Company → Email providers to authorize the exact application, purpose, sender domain, period and row limits.
If no client appears, verify that they used your current provider code and confirmed the authorization. If access is expired, revoked, unavailable or out of rows, the Company must review its scope or issue suitable access. Reloading authorizations retrieves current records; it cannot grant permission or renew an expired authorization.
2. Choose the client, application and authorized use
Open Clients & list validation. In Client, application and authorized use, match the company, site, email purpose and sender domain to the list you intend to check. One company can authorize several sites; choose the one where these people consented. The workspace name may be a historical label and does not determine the selected client.
Check the expiry, per-job row limit and remaining total rows before uploading. A client authorization and an individual recipient’s permission are separate conditions: both must be current and match the intended use.
3. Prepare and upload the list
For Emabled’s console use a UTF-8 CSV with an email or address column. An optional second reference column lets you match results to your records. For example, the following addresses are synthetic; they do not imply consent:
email,reference
person@example.com,customer-001
another@example.com,customer-002
A supported ZIP contains one CSV at its root. CSV/ZIP is a capability of this implementation, not a normative XCIM wire format. The Deploy to Agents report below tested CSV only; the separate historical MuMaps report includes ZIP.
Select List file, review the application and choose Upload and validate. The console counts rows. Keep the page open until it shows that the upload was accepted, then follow the validation status. No backend integration is needed for the console upload; the optional backend/API path is a separate integration.
4. Read permission and public verification separately
| Emabled result | Meaning | Action |
|---|---|---|
EMABLED_CONSENT_ACTIVEactive_matching | The issuer found a verified receipt and current matching permission at evaluation time. | Check scope and validity. This alone is not public XCIM_PASS or permission to bypass your sending policies. |
XCIM_NONEno_evidence | No matching permission evidence was established. | Do not assume consent, fabricate a receipt or transfer another site’s permission. |
XCIM_REVOKED | Permission was withdrawn in the historical managed lifecycle test. | Apply the withdrawal. Deploy to Agents did not repeat that lifecycle test. |
Public proof unavailable / XCIM_STATUS_INDETERMINATE | Sufficient public verification was not established. | Preserve the uncertainty; do not relabel an issuer permission result as independently verified XCIM. |
Open the completed job and download its CSV for each row’s classification, code, evaluation time, validity limit and public-proof status. The two-row Deploy to Agents test returned one matching permission and one no-evidence control; the matching row’s public proof was unavailable. Re-evaluate before relying on a result after its validity period or after permission changes.
5. Correct problems without changing consent
When a file is rejected for a format problem, read the error, correct the header, encoding or affected rows in the original list, and select the corrected file. Recheck the available row budget before submitting again. A new file does not undo a job already accepted or create permission for an address.
If a row has no matching consent, first check the selected site, purpose, sender domain and address. Fix incorrect input where appropriate; otherwise the company needs to collect a real decision from the person. Do not change an address or scope merely to force a positive result.
Emabled retains jobs and encrypted files for 24 hours. Results require current authorization when downloaded. Save the necessary result privately under your own retention policy; avoid putting addresses, tokens or receipts in public reports. A browser reload can reopen an accepted job; it is not a reason to re-upload the same list.
Before using the list
Apply your own sending policy, sender checks and suppression handling. Consent evidence does not prove mailbox existence, guarantee delivery or settle a complaint automatically. The Company retains responsibility for withdrawal and sender scope; the ESP retains responsibility for its policy decisions.
Deploy to Agents results and limits · Emabled CSV template · Product integration documentation
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.