Submission for analysis
Once all documents are properly attached, the analysis must be triggered, which sends all the data to our anti-fraud system for a compliance review. If it is rejected, a new analysis must be carried out. If it is approved, there is a subsequent internal representative validation stage, in which the assignor's signer structure is also assembled, so that the operation with them can finally begin, enabling the creation of master contracts between the assignor and the fund.
| Profile | Host | Required permission |
|---|---|---|
| Manager | manager-api | Write |
| Consultant | consultant-api | Register Assignor |
| Assignor | assignor-api | Write |
Base URL for each host: Environments (Hosts).
Request
{
"analysis_status":"sent_to_analysis"
}
Body Params
| Field | Type | Description | Characters |
|---|---|---|---|
analysis_status * | string | New analysis status to be submitted (must be equal to sent_to_analysis). | 1 to 50 |
*Required field.
Response
The body is the full analysis, in the same format as the Analysis Query. Excerpt:
{
"analysis_key": "2b1fa466-4d36-48e9-b6e3-776a1b700b9f",
"analysis_number": 1,
"assignor_registry_key": "d0a93900-457d-496a-8326-480ecaf946c3",
"assignor_registry_status": "pending_registry",
"status": "sent_to_analysis"
}
An analysis must only be effectively submitted after all the relevant documents have been attached. Once the analysis is submitted, it will no longer be possible to attach new documents.
An analysis that goes 1 month without activity and has not yet been concluded is canceled automatically (canceled). The most common case is an analysis left in pending_documents. Once canceled, it can no longer be triggered: the attempt is rejected with ASR000034. In that case, generate a new analysis through the Registration Update.
Errors
| Status | Code | When it happens |
|---|---|---|
| 404 | ASR000004 | Assignor not found for the assignor_registry_key provided. Check whether the assignor_registry_key is correct (or, for the manager and the consultant, whether the registration belongs to your integration). |
| 404 | ASR000033 | Analysis not found for the analysis_key provided. Check whether the analysis_key is correct. |
| 400 | ASR000040 | The analysis does not belong to the assignor provided. Make sure analysis_key and assignor_registry_key refer to the same analysis. |
| 400 | ASR000034 | The analysis cannot receive this status. The analysis can only be submitted while it is in the pending_documents status. Check the current status in Analysis Query. If it is canceled, it was canceled due to inactivity and a new analysis must be generated. |
| 400 | ASR000038 | The status submitted is invalid. The analysis_status field must be exactly sent_to_analysis. |
| 400 | ASR000009 | The analysis does not have all the assignor's required documents. Attach the documents required for the assignor's person type before triggering the analysis. See Document Submission. |
| 400 | ASR000015 | An analysis related party does not have all the required documents. Attach the required documents of the related party indicated by the analysis_related_party_key in the error before triggering the analysis. |
Authentication, permission and host errors: see API Errors.