| All Verbs | /mobile/maps/news |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Category | query | string | No | |
| Dateini | query | DateTime? | No | |
| Datefin | query | DateTime? | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Code | form | string | No | |
| ErrorMessage | form | string | No | |
| Data | form | List<NewsData> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| code | form | int | No | |
| datenews | form | DateTime | No | |
| category | form | string | No | |
| title | form | string | No | |
| intro | form | string | No | |
| author | form | string | No | |
| image | form | string | No | |
| news | form | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /mobile/maps/news HTTP/1.1
Host: ws.jimsnwa.com
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
Category: String,
Dateini: 0001-01-01,
Datefin: 0001-01-01
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
Code: String,
ErrorMessage: String,
Data:
[
{
code: 0,
datenews: 0001-01-01,
category: String,
title: String,
intro: String,
author: String,
image: String,
news: String
}
]
}