Request Adhesion Term
Introduction
This resource is used to create a request for an investor's adhesion term to a fund's issuance series. From this request, the documents needed to formalize the adhesion are generated, according to the issuance series settings.
Input / Output:
As input, the UUID of the issuance series the investor is adhering to must be sent and, optionally, the signature method to be used for the generated documents.
As output, an investor_adhesion_key is delivered. The investor_adhesion_key is used to identify the investor adhesion.
Available on
| Profile | Host | Required permission |
|---|---|---|
| Manager | manager-api | Write |
| Consultant | consultant-api | Create Adhesions |
The issuance series must belong to a fund of the manager (or, for the consultant, to a fund in which it has this permission).
Base URL for each host: Environments (Hosts).
Request
ENDPOINT
/investor_adhesion/investor/INVESTOR_KEY/investor_adhesionMETHOD
POSTSTATUS
201Request body
Request Body
{
"issuance_serie_key": "UUID",
"signature_method": "qi_sign",
"signer_group_key": "UUID"
}
Investor Adhesion
| Field | Type | Description | Characters | Required |
|---|---|---|---|---|
issuance_serie_key | string | Key of the issuance series the investor is adhering to | 36 | Yes |
signature_method | string | Enumerator of the signature method to be used in the documents. If omitted: qi_sign for a natural person and certifiqi for a legal entity | - | No |
signer_group_key | string | Key of the investor's signer group. If omitted, the investor's default signer group is used | 36 | No |
Signature Method
| Enumerator | Description |
|---|---|
certifiqi | Signature via CertifiQi (Digital Certificate) |
qi_sign | Signature via QI Sign (Electronic Signature) |
Response
Response Body
{
"investor_adhesion_key": "UUID"
}
Adhesion flow
- If all documents required by the series already exist and are valid, the adhesion is created directly in the
activestatus. - Otherwise, the adhesion is created in the
pending_documentsstatus and remains so until the required documents are generated and signed. - If the investor already has an
active,pending_documentsorpending_batch_closeadhesion for the same issuance series, the request is rejected withIAD000014.
Errors
| Status | Code | When it happens |
|---|---|---|
| 400 | IAD000027 | The investor's classification (general, qualified, professional) does not allow adhering to the series |
| 400 | IAD000042 | The investor's registration is pending update |
| 400 | IAD000045 | The investor has no active suitability |
| 400 | IAD000051 | The investor has no signer group (or the given signer_group_key does not exist) |
| 400 | IAD000054 | The investor is non-operational |
| 400 | QIT000011 | The issuance series does not belong to a fund of the manager |
| 403 | IAD000049 | The consultant does not have the permission to create adhesions in the series' fund |
| 404 | IAD000012 | Investor not found (on manager-api, the response currently comes as IAD000010) |
| 404 | IAD000018 | Issuance series not found |
| 404 | IAD000040 | signature_method not found |
| 409 | IAD000014 | The investor already has an active adhesion or one waiting for signature for this issuance series |
| 409 | IAD000057 | The investor already has a link with this issuance series |
Authentication, permission and host errors: see API Errors.