Creates a user that belongs to the buyer that the logged-in user belongs to. To Create an Authorised User you would need a stepped-up token. After calling this endpoint you need to step-up ( issue a challenge /stepup/challenges/otp/{channel} ). More details on how to step-up a token can be found here Step-Up.
Once on-boarded, users have access and manage the buyer's payment runs.
Users are assigned roles which limit the level of access they have and what they can do on behalf of the buyer.
Required user role: ADMIN
Security
apiKey and authToken
Roles define the level of access assigned to the user.
CREATOR: Users assigned this role can create, view and update payment runs.CONTROLLER: Users assigned this role can view and link their company's bank accounts as well as fund payment runs.
Items Enum:"CREATOR""CONTROLLER"
- Sandboxhttps://sandbox.weavr.io/payment-run/v1/users
- Mock serverhttps://api.weavr.io/_mock/products/payment-run/openapi/v1/users
curl -i -X POST \
https://sandbox.weavr.io/payment-run/v1/users \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'api-key: YOUR_API_KEY_HERE' \
-H 'idempotency-ref: string' \
-d '{
"name": "string",
"surname": "string",
"email": "user@example.com",
"mobile": {
"countryCode": "string",
"number": "string"
},
"dateOfBirth": {
"year": 1900,
"month": 1,
"day": 1
},
"roles": [
"CREATOR"
]
}'Success
The state of the user. If the active attribute is false, then the user will not be able to log in.
Roles define the level of access assigned to the user.
CREATOR: Users assigned this role can create, view and update payment runs.CONTROLLER: Users assigned this role can view and link their company's bank accounts as well as fund payment runs.
Items Enum:"CREATOR""CONTROLLER"
Response
{ "id": "string", "buyerId": "string", "name": "string", "surname": "string", "email": "user@example.com", "mobile": { "countryCode": "string", "number": "string" }, "active": true, "dateOfBirth": { "year": 1900, "month": 1, "day": 1 }, "roles": [ "CREATOR" ], "addedBy": { "rolesNames": [ … ], "userId": "string" } }