| GET, POST | /fibuscan/OnlinehandelTreffertypen |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| expression | body | string | No | |
| limit | body | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Liste | form | List<onlinehandel_treffertypen> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| id | form | long? | No | |
| guid | form | string | No | |
| mandant | form | long? | No | |
| del | form | long? | No | |
| parent_id | form | long? | No | |
| soll_parsen | form | long? | No | |
| bezeichnung | form | string | No | |
| _erstellt | form | DateTime? | No | |
| _aenderung | form | DateTime? | No | |
| suchfeld1 | form | long? | No | |
| suchfeld1_text | form | string | No | |
| suchfeld2 | form | long? | No | |
| suchfeld2_text | form | string | No | |
| PrimaryKey | form | long? | 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 /fibuscan/OnlinehandelTreffertypen HTTP/1.1
Host: ws4.fibudata.net
Accept: application/json
Content-Type: application/json
Content-Length: length
{"expression":"String","limit":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Liste":[{"id":0,"guid":"String","mandant":0,"del":0,"parent_id":0,"soll_parsen":0,"bezeichnung":"String","_erstellt":"\/Date(-62135596800000-0000)\/","_aenderung":"\/Date(-62135596800000-0000)\/","suchfeld1":0,"suchfeld1_text":"String","suchfeld2":0,"suchfeld2_text":"String","PrimaryKey":0}]}