Submit completed BigDataCorp KYC to Avenia
Finalizes a completed BigDataCorp capture by fetching the provider images and identity data on demand, forwarding them to Avenia, and moving the Pods KYC profile to provider_pending when Avenia accepts the submit. Repeated requests while the Avenia submission is in progress return the existing provider_pending state and do not duplicate document uploads. A durable Pods background task continues to refresh the Avenia attempt after the response. If Avenia rejects the final submit before a normal pending attempt is created, Pods persists the provider failure on the KYC profile as rejected_retryable so GET /api/v1/kyc/status can return providerResult and providerMessage. Pods does not persist full CPF, address, raw images, or base64 payloads.
Authorizations
API key for authentication. Obtain from your Pods dashboard.
Body
Final BigDataCorp KYC submission payload
Pods-generated KYC user id returned by the BigDataCorp session endpoint
"550e8400-e29b-41d4-a716-446655440000"
Address data forwarded to Avenia during the final BigDataCorp KYC submit. Pods does not persist this address.
Optional applicant phone forwarded to Avenia
"+5511999999999"
Response
BigDataCorp KYC submitted to Avenia
BigDataCorp KYC submission result