source
Developers

Complementary integrations. Availability is confirmed per assessment.

SOURCE is designed to sit beside ERP, PIM, PLM, and DPP platforms — not to replace them. File import and export are the current public capabilities. APIs, webhooks, and named connectors are targets whose availability must be confirmed.

Request an evidence assessment
Current

Files in, files out.

The discovery workspace demonstrates import of catalogue extracts and export of the evidence trail. That is what can be discussed as available without a scoped assessment.

  • File import of product identity, claim values, and existing evidence.
  • File export of readiness, unresolved reasons, and the evidence trail.
  • Spreadsheet and catalogue extracts as the default interchange.
Targets

Versioned API and webhooks, if they are in scope.

The shapes below describe the intended integration surface. They are not a general-availability announcement. Confirm each endpoint, webhook, and named connector during assessment.

Intended resources

  • /v1/actors
  • /v1/products
  • /v1/relationships
  • /v1/claims
  • /v1/evidence
  • /v1/permissions
  • /v1/requests

Intended events

  • claim.updated
  • evidence.expiring
  • request.completed
  • permission.granted
  • identity.resolved
{
  "claim_id": "clm_9f3a",
  "subject_id": "AL-FRAME-881",
  "property": "recycled_content",
  "value": 67,
  "unit": "%",
  "identity_status": "reconciled",
  "readiness": "UNRESOLVED",
  "unresolved_reason": "permission_denied",
  "reuse_permission": "denied"
}