PACINBack to PACIN

Docs Fundamentals Consent

Consent

Required for live data. Not optional.

The institution captures consent from the applicant. PACIN stores the record. Live ingest and scoring check it before they run.

PACIN does not run the applicant’s screen. You do. Then you register the consent with PACIN.

Create

bash
curl -X POST https://app.pacinnetwork.com/api/v1/consents \
  -H "Authorization: Bearer $PACIN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "purpose": "credit_assessment",
    "entity_id": "pac_KE_0001"
  }'

Purpose is typically credit_assessment. Only active consents allow live operations. List and filter with GET /v1/consents.

Revoke

DELETE /v1/consents/{consent_id} marks the consent revoked. Further scoring for that pair should stop. A new consent is required to start again.

After consent: ingest data, then score.

Last updated 14 September 2026