| GET | /users/{UserId}/visit-history | Get user visit history |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ApiKey | query | string | Yes | Api Key - grants access to resources |
| UserId | query | integer | Yes | |
| StoreId | query | string | No | StoreId OR ChainId is required |
| ChainId | query | string | No | StoreId OR ChainId is required |
| FromDate | query | date | Yes | (Format:YYYY-MM-DD) |
| ToDate | query | date | Yes | Max 31 Days (Format:YYYY-MM-DD) |
| RestrictedId | query | int? | No | |
| RestrictedResourceType | query | RestrictedResourceType | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserId | form | int | No | |
| FromDate | form | DateTime | No | |
| ToDate | form | DateTime | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ApiKey | form | string | No | |
| StoreId | form | int? | No | |
| ChainId | form | int? | No |
| Store | |
| Chain | |
| User | |
| Undefined |
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.
GET /users/{UserId}/visit-history HTTP/1.1
Host: clubready.com
Accept: application/json