Authorizations
The authentication system on Partoo API is using API Key that should be put in the header of the request (the name of the header is x-APIKey
). An api_key is linked to a user. This user's role will give you different access level to the API features.
Body
Request body to create a user
User email (must be unique will return otherwise)
User first name
"Perceval"
User last name
"de Galles"
Id of the organization to which the user should belong. If no org_id
given, the user will have the same organization as you.
List of (list of Group ID).
Accesses of the users for the new groups system, only for GROUP_MANAGER
users.
[[1, 2], [1, 3]]
The list of business to which the user has access to. Will be taken into account only if user has BUSINESS_MANAGER
role.
User phone number
User role in the application
ORG_ADMIN
, GROUP_MANAGER
, BUSINESS_MANAGER
, PUBLISHER
"BUSINESS_MANAGER"
List of features the user can access from the sidebar.
If not provided in the payload or set to null
, then the user will be given all the available features of their organization.
Send an invitation email to the User.
If you want to have an invited
user but send the invitation email later, you have to send the send_invitation
parameter as False
and a status
parameter to invited
.
You will then have to call the invitation endpoint to send the invitation email to the user.
User status in the application
active
, invited
"active"
The User password. It should comply with the following rules:
- should be at least 8 characters long
- should have one upper case letter and one lower case letter
- should have one special character
8
Available language in the application
fr
, en
, es
, it
, pt-br
, de
, ar
, nl
, pl
, cs
, ca
, sk
, pt
, lv
, ro
, bg
, hu
"fr"
Prevent the user from connecting directly from the Partoo connection page.
This field is available for users whose organization has defined an SSO configuration.
This field can be edited by a user with the role ORG_ADMIN
or PROVIDER
.