| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| EnumProp | query | Dictionary<EnumType, EnumType> | No | |
| EnumWithValues | query | Dictionary<EnumWithValues, EnumWithValues> | No | |
| NullableEnumProp | query | Dictionary<Nullable<EnumType>, Nullable<EnumType>> | No | |
| EnumFlags | query | Dictionary<EnumFlags, EnumFlags> | No | |
| EnumStyle | query | Dictionary<EnumStyle, EnumStyle> | No |
| Value1 | |
| Value2 | |
| Value3 |
| Name | Value | |
|---|---|---|
| None | None | |
| Value1 | Member 1 | |
| Value2 | Value2 | Member 2 |
| Name | Value | |
|---|---|---|
| Value0 | 0 | |
| Value1 | 1 | |
| Value2 | 2 | |
| Value3 | 4 | |
| Value123 | 7 |
| lower | |
| UPPER | |
| PascalCase | |
| camelCase | |
| camelUPPER | |
| PascalUPPER |
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 /json/oneway/HelloWithEnumMap HTTP/1.1
Host: test.servicestack.net
Accept: application/json
Content-Type: application/json
Content-Length: length
{"enumProp":{"Value1":"Value1"},"enumWithValues":{"None":"None"},"nullableEnumProp":{"Value1":"Value1"},"enumFlags":{"0":0},"enumStyle":{"lower":"lower"}}