All Verbs | /service/ImportSalesGoals |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
items | query | List<SalesGoalImport> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
rep | form | string | No | |
vendor | form | string | No | |
category | form | string | No | |
goalType | form | string | No | |
year | form | int | No | |
jan | form | decimal | No | |
feb | form | decimal | No | |
mar | form | decimal | No | |
apr | form | decimal | No | |
may | form | decimal | No | |
jun | form | decimal | No | |
jul | form | decimal | No | |
aug | form | decimal | No | |
sep | form | decimal | No | |
oct | form | decimal | No | |
nov | form | decimal | No | |
dec | form | decimal | No |
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 /service/ImportSalesGoals HTTP/1.1
Host: www.bernhardthospitality.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"items":[{"rep":"String","vendor":"String","category":"String","goalType":"String","year":0,"jan":0,"feb":0,"mar":0,"apr":0,"may":0,"jun":0,"jul":0,"aug":0,"sep":0,"oct":0,"nov":0,"dec":0}]}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {}