Create investor / investor analysis

---

Introduction

This resource aims to inform us of basic data to start the registry analysis of an investor. There are 2 types of registry analysis: natural person and legal person. Legal persons, in turn, have sub types, which are used to distinguish the necessary information during registration.

Information

In the Sandbox environment, we have the following rule for approvals: CPF/CNPJ starting with 1: Automatic rejection; CPF/CNPJ starting with 8: Pending Manual Validation; The rest are automatically approved.

Registration Flow

Legal person investor registration follows these steps:

1. Create Investor - Initial investor creation and registry analysis
2. Send Registry Data - Specific legal person data
3. Send Address - Address information
4. Send Assets - Net worth data
5. Send Bank Accounts - Bank account information
6. Send Suitability - Suitability questionnaire (mandatory for retail investors)
7. Send Subscriber Groups - Definition of subscriber groups
8. Send Investor Documents - Upload of mandatory documents
9. Create Related Parties - Registration of partners, directors, administrators, etc.
10. Send Related Parties Documents - Upload of related parties documents
11. Send for Analysis - Submission for registry analysis
12. Sign Documents - Document signing after approval

Input / Output:

Each type of registry analysis expects a set of data as input. Below are examples of how to initiate each of these flows.

As output, an investor_key and an investor_analysis_key will be delivered. The investor_analysis_key is used to identify the created registry analysis. The investor_key is used to identify the investor to which the registry analysis belongs.

Thus, a single investor_key (investor) can be associated with one or more investor_analysis_key (registry analysis).

Both the investor_key and the investor_analysis_key will be used in other endpoints that interact with the investor or with the registry analysis.

Request

ENDPOINT

/investor_registry/v2/investor

METHOD

POST

STATUS

201

Request body

Request Body

{
    "name": "string",
    "document_number": "xx.xxx.xxx/xxxx-xx",
    "person_type": "legal_person | natural_person",
    "person_sub_type": "regular | fund_class",
    "external_distribution_key": "campo livre",
    "email": "string",
    "phone": {
	    "international_dial_code": "+xx",
	    "area_code": "xx",
	    "number": "xxxxxxxxxx"
    }
}

Attention

Required fields change according to person_type.

• If natural_person (natural person):

  • The fields name, document_number, person_type, email and phone are mandatory

• If legal_person (legal person):

  • The fields name, document_number, person_type

• If nominee (PCO):

  • The fields name, person_type, external_distribution_key are mandatory

Information

The registry_user is the entity that represents the user who will fill in the investor's registry data. In the case of natural person, the investor themselves fills in their registry data.

Case 02: Register Legal Person

Request Body

{
  "name": "Fundo XPTO", 
  "document_number": "12.456.789/0001-00", 
  "person_type": "legal_person",
  "person_sub_type": "regular",
  "registry_user": {
    "name": "José da Silva", 
    "document_number": "123.456.789-00",
    "email": "example@example.com",
    "phone": {
        "international_dial_code": "55",
        "area_code": "11",
        "number": "1234567890"
    },
  }
}

Body params

Field	Type	Description	Characters	Required
name	string	Investor name	1 - 255	Yes
document_number	string	CPF or CNPJ	13 - 18	Yes
person_type	string	Person Type enumerator	-	Yes
person_sub_type	string	Person Sub Type enumerator	-	Yes
email	string	Email	1 - 255	No
phone	JSON	Phone object	-	No
registry_user	JSON	Registry User object	-	No

Phone

Field	Type	Description	Characters	Required
international_dial_code	string	International code	1 - 3	Yes
area_code	string	Area code	2	Yes
number	string	Phone number	8 - 9	Yes

Registry User

Field	Type	Description	Characters	Required
name	string	Registry user name	1 - 255	Yes
document_number	string	CPF	13	Yes
person_type	string	Person Type enumerator	-	Yes
email	string	Email	1 - 255	Yes
phone	JSON	Phone object	-	Yes

Person Type

Enumerator	Description
natural_person	Natural person
legal_person	Legal person

Person Sub Type

Enumerator	Description
regular	-
fund_class	Investment fund

Response

Response Body

{
    "investor_key": "UUID",
    "investor_analysis_key": "UUID"
}