Table of Contents |
---|
Introduction
In instances where there is a need to create a new broker within a specific account utilizing the Thinksurance Public API V1, henceforth referred to as "the API," a dedicated endpoint facilitates this capability. This endpoint is accessible at the path /api/broker/set/{:token}. It anticipates a comprehensive payload as part of the HTTP request, encompassing the requisite broker data.
Endpoint
To create a broker via the API, it is imperative to send an HTTP POST request to the endpoint /api/broker/set/{:token}. The parameterised segment of the endpoint, denoted as "{:token}," contains to the security token retrievable by the partner during the Authentication process on the API. The rest of the HTTP request is a JSON payload of the request body.
Action name | create broker |
---|---|
HTTP path | /api/productsbroker/set/{:token}
|
HTTP method | POST |
Attributes of the HTTP request
...
Broker Parameters
The initial set of parameters pertains to broker data. Only specific elements within this data subset are mandatory for delivery. These required elements assist the API in providing critical information for the broker creation.
aToken | string | required | A |
---|
professionId
int
optional
An attribute used to filter out all products for particular profession.
special token used for accounts to identify itself during API calls. Provided by Thinksurance Support Team. | |||||||||||
type | int | required | Enumeration value that defines the way for mapping broker data from the request:
| ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
bExternalId | string | required | Broker’s ID from the partner system. | ||||||||
bGender | int | optional | Enumeration value that defines salutation of the broker person:
| ||||||||
bFirstName | string | optional | Broker person’s first name. | ||||||||
bLastName | string | required1 | Broker person’s last name. | ||||||||
bEmail | string | required | Broker person’s email address. | ||||||||
bCompany | string | required2 | Broker company’s name. | ||||||||
bStreet | string | optional | Broker company’s street name. | ||||||||
bStreetNumber | string | optional | Broker company’s street number. | ||||||||
bZip | string | optional | Broker company’s postcode. | ||||||||
bCity | string | optional | Broker company’s city. | ||||||||
bPhone | string | optional | Broker company’s phone number. | ||||||||
bCompanyRegNumber | string | optional | Broker company’s commercial register number. | ||||||||
bRegNumber | string | optional | Broker company’s IHK register number. | ||||||||
Explanations:
1 required if bCompany is not set |
Attributes of the HTTP response
Success response | ||||
---|---|---|---|---|
JSON array of objects containing: | ||||
idstatus | intstring | required | An unique identifier of the product. | nameA text providing more information on the succesful operation. |
bToken | string | requiredA | product’s nameAn identifier for the new broker. | |
Failed response | ||||
error | string | required | It contains a reason for the failed request. |
Examples
...
HTTP Request without profession filter
...
As previously stated, to execute Broker Create, it is imperative to dispatch a POST HTTP request to the /api/broker/set/{:token} endpoint of the API. Below, instances of potential communication between the API and consumers are provided.
HTTP Request with minimal data for company | |||||
| |||||
HTTP Request with profession filterminimal data for a person | |||||
| |||||
Successful HTTP Response | |||||
| |||||
Failed HTTP Response | |||||
|
...