Skip to main content
POST
Issues a new invite for a KYC source. The new invite carries a new token, your current record key and the source’s current profile key. The request has no body.
The old token stops working at once. Until the verifier stores the new invite, its calls to the inbox answer 401 UNAUTHORIZED. Hand the new invite over through a confidential channel, as with the first one.
Issue a new invite when:
  • you replaced the record key with Set Record Key. The verifier’s tool pins the key from its invite and refuses to send while the inbox reports another one.
  • you changed the source’s profileKey with Update KYC Source.
  • the invite may have reached someone other than the verifier.
Records already delivered are not affected. On the verifier’s side a new invite for a source that already has one is stored with trusset-kyc invite add --replace --fingerprint "<fingerprint>", with the fingerprint you read out from trusset-kyc key show over a separate channel.

Path Parameters

string
required
The source id from List KYC Sources.

Response Fields

object
The response is sent with Cache-Control: no-store. The call is written to the customer audit log as KYC_SOURCE_INVITE_ISSUED.

Error Codes