| POST | /Crm/Contracts/TspAttorneyfiles |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Iud | body | int | No | |
| AttFileId | body | int? | No | |
| AttId | body | int? | No | |
| Name | body | string | No | |
| FileStream | body | byte[] | No | |
| ThFileStream | body | byte[] | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | int? | 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 /Crm/Contracts/TspAttorneyfiles HTTP/1.1
Host: 10.10.0.107
Accept: application/json
Content-Type: application/json
Content-Length: length
{"Iud":0,"AttFileId":0,"AttId":0,"Name":"String","FileStream":"AA==","ThFileStream":"AA=="}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}},"Result":0}