🚧
Advanced KYC ONLY
Only use this endpoint if you are utilizing the new Advanced KYC.

Request

Authorization / Authentication

Apps using Access Token Authorization

Use a valid access token in an Authorization: Bearer request header.

See Auth Token Overview for more details.

NOTE: Though we recommend using JWT, you can use this endpoint with ECDSA.

PUT /0.2/resume_verification HTTP/1.1
sandbox.silamoney.com
Content-Type: application/json
Authorization: Bearer [GENERATED JWT TOKEN HERE]

{
  "header": {
    "created": 1234567890, //required
    "app_handle": "handle.silamoney.eth", //required
    "user_handle":"user.silamoney.eth", //required
    "version": "0.2", 
    "reference": "<your unique id>"
  }, 
    "verification_uuid": <uuid of KYCRequest>, //required
    "update": <"entity" or "document">, //required
    "doc_ids": [<optional list of document uuids>] //required following document uploads; optional if updating entity data only
}

***

HTTP/1.1 200 OK

{
  "success": True,
  "verification_uuid": <verification_uuid requested>,
  "message": "Verification successfully resumed."
}

Request Attributes

Key	Type	Description
header	JSON object	Required. Required keys: `created` - Unix epoch timestamp in seconds. Must not be future-dated and must not be dated more than 5 minutes in the past. `app_handle` - your app handle `user_handle` - user_handle to resume verification for. Optional keys: `reference`: Can be any value for your own reference. If not provided, one will be assigned. `version`: Cannot be null if key is present. Valid values: 0.2, v0.2, V0.2
verification_uuid	string	Required. UUID of verification to resume. Can be found by calling /get_verifications.
update	string	Required. Valid options: `entity`: if entity PII has been updated `document`: if documents have been uploaded.
doc_ids	string	Required if resuming a verification following uploading documents to /documents. Optional if resuming a verification following updating entity data only. List of document UUID's returned from /documents.

Responses

Status Code	Success Attribute	Description
200	`true`
400	`false`	Missing required data from the request. "Missing required data: ."
400	`false`	When a document resumption is requested without any docs uploaded. "No documents provided for resuming verification."
400	`false`	When the document had the same side uploaded multiple times. "Duplicate document sides provided."
400	`false`	Alloy fails to resume the verification and returns something other than a 200. "Alloy failed to resume verification with a status code {status_code}." Reach out to Sila support.
404	`false`	When a non-existent verification_uuid is entered. "Verification {uuid} not found."
404	`false`	When a verification record is not in a state that can be resumed. "Journey application not ready to be resumed."

🚧Advanced KYC ONLY

Request

Authorization / Authentication

Apps using Access Token Authorization

Request Attributes

Responses

🚧
Advanced KYC ONLY