| POST | /salesReps/{brand}/{posCode} | Create Sales Reps |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| brand | path | string | Yes | Brand Triagram, e.g. CAR, IWC, VAC |
| posCode | path | string | Yes | Point of Sale Code, e.g. ES100:102048 |
| firstName | body | string | Yes | First name of sales representative |
| lastName | body | string | Yes | Last name of sales representative |
| body | string | Yes | Email address of sales representative |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| userId | form | Guid | Yes | Booster user ID of sales representative |
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 /salesReps/{brand}/{posCode} HTTP/1.1
Host: dev-api-booster.richemont.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"brand":"String","posCode":"String","firstName":"String","lastName":"String","email":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"userId":"00000000000000000000000000000000"}