| POST | /user/{brand}/{userId}/authorize | Create the authorization for the given external user and for the given POS Codes | The 'CreateUserAuth' API is not implemented for internal users |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| userId | path | string | Yes | User's UserID (GUID). E.g. '731cd7f3-a781-48bf-b43d-310273895ce2' |
| brand | path | string | Yes | Brand Trigram, e.g. CAR, IWC, VAC |
| authRequests | body | List<AuthRequest> | Yes | Authorization requests for the provided user |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| posCode | form | string | Yes | POS Code (only for external users) |
| roles | form | List<Guid> | Yes | Roles for users (GUIDs). E.g. '731cd7f3-a781-48bf-b43d-310273895ce2' |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /user/{brand}/{userId}/authorize HTTP/1.1
Host: dev-api-booster.richemont.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"userId":"String","brand":"String","authRequests":[{"posCode":"String","roles":["00000000000000000000000000000000"]}]}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{}