Skip to content
Webhooks
/
/
PERSON_DELETED

Webhooks (1.0)

Download OpenAPI description
webhooks.json
webhooks.yaml
Languages
Servers
Mock Server

https://docs.solarisgroup.com/_mock/api-reference/onboarding/webhooks/

Webhook subscription

Operations

Webhook events

Webhooks

PERSON_CHANGEDWebhook

Request

One or more attributes of a person were changed. This webhook does not come with a payload. The header will contain the ID of the person that was changed.

Headers
Solaris-Entity-Idstring

Contains the ID of the person whose data changed.

Example: c724a8d510c5294affadf8c95a8119b5cper
Bodyapplication/json
object
application/json
{}

Responses

Return 200 to indicate that you successfully received the webhook notification.

PERSON_DELETEDWebhook

Request

This webhook event occurs when Solaris deletes all personal data related to the given person from its system according to GDPR regulations.
Note: Solaris is legally required to delete records of created persons who did not become customers within 90 days of collecting the personal data according to GDPR regulations. When you receive a notification of this type, you must immediately delete all data related to the person specified in the webhook notification.

Headers
Solaris-Entity-Idstring

Contains the ID of the person whose data you must delete.

Example: c724a8d510c5294affadf8c95a8119b5cper
Bodyapplication/json
object
application/json
{}

Responses

Return 200 to indicate that you successfully received the webhook notification.

PERSON_MOBILE_NUMBER_CREATEDWebhook

Request

A mobile number was created for a customer, but has not yet been verified. This webhook does not contain a payload, but the header will contain the id of the person for whom the mobile number was created.

Bodyapplication/json
object
application/json
{}

Responses

Return 200 to indicate that you successfully received the webhook notification.