Skip to main content

AsyncIssuanceRequestInput

Represents the input required for creating an async issuance request.

input AsyncIssuanceRequestInput {
  callback: Callback
  claims: JSONObject
  contact: AsyncIssuanceContactInput
  contractId: UUID!
  expirationDate: DateTime
  expiry: AsyncIssuanceRequestExpiry!
  faceCheckPhoto: String
  identity: IdentityInput
  identityId: UUID
  identityVerification: IdentityVerificationDetailsInput
  photoCapture: Boolean
  postIssuanceRedirectUrl: URL
  requiresIdentityVerification: Boolean
  verificationMethods: [VerificationMethodInput!]
}

Fields​

AsyncIssuanceRequestInput.callback ● Callback input​

The callback to register.

AsyncIssuanceRequestInput.claims ● JSONObject scalar​

The collection of assertions made about the subject in the verifiable credential.

Item of note:

  • You must fulfill the contract claims definition. Review contract creation for more information.

AsyncIssuanceRequestInput.contact ● AsyncIssuanceContactInput input​

The issuee's contact information for notification and OTP verification. When not set, no issuance notification is sent and the issuance can *only* be redeemed by signing-in to the Concierge with an existing credential.

AsyncIssuanceRequestInput.contractId ● UUID! non-null scalar​

The ID of the contract you wish to issue.

AsyncIssuanceRequestInput.expirationDate ● DateTime scalar​

Setting the expiration data allows for explicitly control over credential expiry, regardless of when it is issued.

Items of note:

  • The date must be in ISO format.

AsyncIssuanceRequestInput.expiry ● AsyncIssuanceRequestExpiry! non-null enum​

The point in the future which the issuees can no longer complete the issuance process.

Items to note:

  • The period starts upon receipt of the request.
  • No further issuances are possible once expired.
  • Data associated with a request is automatically removed upon issuance or expiry.

AsyncIssuanceRequestInput.faceCheckPhoto ● String scalar​

The issuee's photo for use with face check presentation verification.

Items of note:

  • _Optional:_ When no photo is set and the contract does not require one, the issuance process does not require a photo.
  • The photo is displayed via the authenticator app.
  • The photo must be encoded using the data URL format, and the base-64 encoded image must be of a JPEG type.
  • Image data can only be provided by a single source, either from the faceCheckPhoto or the photoCapture fields.
  • When the contract **requires** face check, either the **faceCheckPhoto** or the **photoCapture** property must be set.
  • When the contract **requires no** face check, neither the **faceCheckPhoto** nor the **photoCapture** property can be set.

AsyncIssuanceRequestInput.identity ● IdentityInput input​

The identity to issue to.

Items of note:

  • _Required_ When not using the identityId property

AsyncIssuanceRequestInput.identityId ● UUID scalar​

The ID of the identity to issue to.

Items of note:

  • _Required_ When not using the identity property.

AsyncIssuanceRequestInput.identityVerification ● IdentityVerificationDetailsInput input​

(Legacy v1) Expected given name and surname for the issuee. Prefer setting these on the idvTrinsic payload of verificationMethods instead.

AsyncIssuanceRequestInput.photoCapture ● Boolean scalar​

When set to true, the issuee is required to capture their photo during the issuance process.

Items of note:

  • _Optional:_ When no photo capture is set and the contract does not require one, the issuance process does not require a photo.
  • The captured photo is displayed via the authenticator app.
  • Image data can only be provided by a single source, either from the faceCheckPhoto or the photoCapture fields.
  • When the contract **requires** face check, either the **faceCheckPhoto** or the **photoCapture** property must be set.
  • When the contract **requires no** face check, neither the **faceCheckPhoto** nor the **photoCapture** property can be set.

AsyncIssuanceRequestInput.postIssuanceRedirectUrl ● URL scalar​

The URL to redirect the issuee to after the issuance process is completed.

Items of note:

  • _Optional:_ When no redirect URL is set, the issuee will remain on the success page.

AsyncIssuanceRequestInput.requiresIdentityVerification ● Boolean scalar​

(Legacy v1) When true, the issuee must complete Trinsic identity verification before the credential can be issued. Prefer using verificationMethods with type: idvTrinsic.

Items of note:

  • Only supported for single (non-batch) issuance requests.
  • When set, identityVerification (givenName and surname) must also be provided.
  • Ignored when verificationMethods is provided.

AsyncIssuanceRequestInput.verificationMethods ● [VerificationMethodInput!] list input​

Explicit verification methods for the issuance (v2 model).

Items of note:

  • At least one method is required when this field is set.
  • idvTrinsic cannot be configured on its own — it must be combined with either otp or conciergeSignin, which determine the redemption path.
  • The redemption URL is determined by OTP presence: when otp is included the holder link uses the unauthenticated /issuance/ path (even when conciergeSignin is also configured — OTP takes precedence). When otp is not included, the authenticated /issue/ Concierge path is used instead.
  • conciergeSignin requires the recipient identity to already hold an active credential.
  • When this field is set, the legacy requiresIdentityVerification, identityVerification, and contact.verification fields are ignored.
  • When this field is omitted, the legacy v1 model applies for backwards compatibility.

Member Of​

createAsyncIssuanceRequest mutation