Assurance Evidence Exchange

Invite-only assurance partners submit anonymous aggregate source evidence to Slotted. This phase stores immutable evidence only — no scores, badges, or RFP-facing assurance product in v1.

STOP line: Partner evidence → validation → immutable storage → STOP. Slotted does not compute billing accuracy from this API in v1.

At a glance

What it does

Accepts one anonymous aggregate evidence record per request for Fulfillment Billing Accuracy or Parcel Billing Accuracy.

Who it's for

Approved assurance partners with API keys that include the ASSURANCE_EVIDENCE capability.

Schema version policy

  • Unknown fields are rejected in v1.
  • Additive optional fields require a new minor schema version (for example slotted.assurance.evidence.v1.1).
  • Required-field or meaning changes require a new major version.
  • Stored submissions are interpreted only under the schema version they arrived with.

Authentication

Same partner API key headers as Short List Referral:

HeaderDescription
x-api-access-keyPublic key id
x-api-secret-keySecret shown once at create/rotate

Endpoint

POST /api/v1/partner/assurance/evidence
Content-Type: application/json

Full schemas and synthetic examples: Assurance Evidence API reference.

Envelope

  • schemaVersion: slotted.assurance.evidence.v1
  • externalObservationId — your idempotency key
  • period — UTC calendar month of audited activity (YYYY-MM)
  • evidenceAsOf — ISO-8601 with explicit timezone
  • Required controlled sourceSystem per partner allowlist
  • Structured population, optional exceptions / remediation, required coverage

Idempotency and corrections

  • First valid body → 201 accepted with receipt including submissionId
  • Identical replay → 200 replayed with the same submissionId
  • Same id, different body → 409 IDEMPOTENCY_CONFLICT
  • Corrections use a new externalObservationId plus supersedesExternalObservationId and keep the original period
Contact: Questions or need API access? Email admin@slotted.com.