Skip to main content
POST
Create BigDataCorp KYC iframe session

Authorizations

x-api-key
string
header
required

API key for authentication. Obtain from your Pods dashboard.

Body

application/json

BigDataCorp iframe session creation payload

cpf
string
required

Brazilian CPF. Pods normalizes and hashes this value; the full CPF is not persisted.

Example:

"52998224725"

email
string<email>
required

Applicant email

walletAddress
string
required

Applicant EVM wallet address

Example:

"0xb794F5eA0ba39494cE839613fffBA74279579268"

externalUserId
string

Optional id from your system for support correlation

Example:

"app-user-001"

Response

BigDataCorp iframe session created or approved BigDataCorp KYC profile reused

BigDataCorp session result. Repeated requests for an active capture return the same iframeUrl and iframeSessionId for up to seven minutes. An approved KYC profile reuse returns status approved with null iframe fields; poll the returned kycUserId through the canonical status endpoint.

kycUserId
string<uuid>
required

Pods-generated public KYC user id

Example:

"550e8400-e29b-41d4-a716-446655440000"

iframeUrl
string<uri> | null
required

BigDataCorp iframe URL for document and liveness capture. Pods reuses the same URL for an active capture for up to seven minutes. Null when no capture is needed.

Example:

"https://iframe.bigdatacorp.com.br/550e8400-e29b-41d4-a716-446655440000"

iframeSessionId
string | null
required

Current BigDataCorp onboarding id. Use it as the WebView remount key so a cached iframe cannot be displayed after Pods returns a newer session. Null when no capture is needed.

Example:

"bigdatacorp-onboarding-id"

status
enum<string>
required

Normalized Pods KYC status

Available options:
created,
provider_pending,
approved,
rejected,
rejected_retryable,
blocked
Example:

"created"