Update compliance answers
/v1/compliance/submissions/{submission_id}/resupplyconst submission = await bird.complianceSubmissions.resupply(
"csb_01krdgeqcxet5s7t44vh8rt9mg",
{
answers: [{ key: "business_registration_number", value: "90012769" }],
},
);
console.log(submission.satisfied);submission = client.compliance_submissions.resupply(
"csb_01krdgeqcxet5s7t44vh8rt9mg",
answers=[{"key": "business_registration_number", "value": "90012769"}],
)
print(submission.satisfied)submission, err := client.ComplianceSubmissions.Resupply(context.Background(), "csb_01krdgeqcxet5s7t44vh8rt9mg", bird.ComplianceSubmissionsResupplyParams{
Answers: []bird.ComplianceAnswer{
{Key: "business_registration_number", Value: bird.Ptr("90012769")},
},
})
if err != nil {
log.Fatal(err)
}
fmt.Println(*submission.Satisfied)$submission = $bird->complianceSubmissions->resupply(
'csb_01krdgeqcxet5s7t44vh8rt9mg',
(new ComplianceSubmissionResupply())->setAnswers([
(new ComplianceAnswer())->setKey('business_registration_number')->setValue('90012769'),
]),
);
echo $submission->getSatisfied() ? 'satisfied' : 'outstanding', "\n";bird compliance submissions resupply <submission-id> --body-file - <<'JSON'
{
"answers": [
{
"key": "business_registration_number",
"value": "90012768"
}
]
}
JSONcurl -X POST "https://us1.platform.bird.com/v1/compliance/submissions/{submission_id}/resupply" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"answers": [
{
"key": "business_registration_number",
"value": "90012768"
}
]
}'{
"next": [
{
"kind": "operation"
}
],
"id": "csb_01krdgeqcxet5s7t44vh8rt9mg",
"subject_kind": "sms_sender",
"subject_id": "scr_01krdgeqcxet5s7t44vh8rt9mg",
"program": "alpha",
"country_code": "US",
"identity_id": "cid_01krdgeqcxet5s7t44vh8rt9mg",
"items": [
{
"id": "cit_01krdgeqcxet5s7t44vh8rt9mg",
"state": "not_supplied",
"attachment_id": "tca_01krdgeqcxet5s7t44vh8rt9mg",
"attachment_ids": [
"tca_01krdgeqcxet5s7t44vh8rt9mg"
]
}
]
}
Replaces rejected, expired, or missing answers on an existing submission. Accepted answers normally cannot be changed and should be omitted.
When a verifier requests corrections, you can replace selected accepted answers while that correction remains open and before its deadline. Unchanged entries are ignored, and at least one answer must change. Changed answers are reviewed again; other answers remain unchanged.
The answers are a legal representation under the name of the business they describe. Accepted dossiers can be registered with the carrier or regulator after compliance review.
Parámetros
submission_idstringSubmission ID.
Cuerpo de la solicitud
answersCarga de respuesta
nextWhat to do next about this submission, given the state it is in. Each entry names one action and says why it is worth taking, so you can act on this response without working out the order yourself. Present on reads that compute it: an empty list means there is nothing to do, and the field is absent entirely on responses that do not report next actions.
A submission reports the answers you filed; whether the country's requirements are met is reported by the requirements read. So this points there rather than repeating a verdict it does not own.
idsubject_kindsubject_idprogramcountry_codeidentity_idThe party this registration was filed for, or null if none was named.
satisfiedWhether this country's requirements are met. true once the submission is approved and every required requirement is approved or marked not applicable. This can remain true when an external verifier requests a correction. Once you submit that correction, it must pass review before this becomes true again, including any optional answers you change.
itemsEvery answer and where it stands. Each is decided on its own.
created_atWhen this was submitted.
updated_atWhen it last changed.
closed_atWhen this submission was closed. Null while it remains open.
closure_reasonThe decline reason for a closed submission, or null while open.
Recursos relacionados
Continúa con la documentación, guías y ejemplos de este tema.