POST /organization/user/invitation/send
Feature - A Feature represents a specific functionality like Email
campaign, Deals, Calls, Automations, etc. on Brevo. While inviting a user,
determine which feature you want to manage access to. You must specify the
feature accurately to avoid errors. Permission - A Permission defines the
level of access or control a user has over a specific feature. While
inviting user, decide on the permission level required for the selected
feature. Make sure the chosen permission is related to the selected feature.
Features and their respective permissions are as below: - email_campaigns:
- "create_edit_delete"
- "send_schedule_suspend"
sms_campaigns:- "create_edit_delete"
- "send_schedule_suspend"
contacts:- "view"
- "create_edit_delete"
- "import"
- "export"
- "list_and_attributes"
- "forms"
templates:- "create_edit_delete"
- "activate_deactivate"
workflows:- "create_edit_delete"
- "activate_deactivate_pause"
- "settings"
landing_pages:- "all"
transactional_emails:- "settings"
- "logs"
smtp_api:- "smtp"
- "api_keys"
- "authorized_ips"
user_management:- "all"
sales_platform:- "create_edit_deals"
- "delete_deals"
- "manage_others_deals_tasks"
- "reports"
- "settings"
phone:- "all"
conversations:- "access"
- "assign"
- "configure"
senders_domains_dedicated_ips:- "senders_management"
- "domains_management"
- "dedicated_ips_management"
push_notifications:- "view"
- "create_edit_delete"
- "send"
- "settings"
companies:- "manage_owned_companies"
- "manage_other_companies"
- "settings"
Note: - If
all_features_access: falsethen only privileges are required otherwise iftruethen it's assumed that all permissions will be there for the invited user. - The availability of feature and its permission depends on your current plan. Please select the features and permissions accordingly.
Servers
- https://api.brevo.com/v3
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
all_features_access |
Boolean | Yes |
All access to the features Valid values:
|
email |
String | Yes |
Email address for the organization |
privileges[] |
Array | Yes | |
privileges[].feature |
String | No |
Feature name Valid values:
|
privileges[].permissions[] |
Array | No |
Permissions for a given feature |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.