GET | /api/client/mappings/type/{typeDesc}/target/{target} |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
TypeDesc | path | string | No | |
Target | path | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ClientMappings | form | List<ClientMap> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ClientMapID | form | long | No | |
TheirVal | form | string | No | |
OurVal | form | string | No | |
KeyTypeID | form | int | No | |
KeyTypeDesc | form | string | No | |
TypeID | form | int | No | |
TypeDesc | form | string | No | |
KeyValue | form | int | No | |
MapTarget | form | string | 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.
GET /api/client/mappings/type/{typeDesc}/target/{target} HTTP/1.1 Host: devapi.billhighway.com Accept: application/json
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"ClientMappings":[{"ClientMapID":0,"TheirVal":"String","OurVal":"String","KeyTypeID":0,"KeyTypeDesc":"String","TypeID":0,"TypeDesc":"String","KeyValue":0,"MapTarget":"String"}]}