| GET | /RS/Spec/SpecSSAFs | ||
|---|---|---|---|
| GET | /RS/Spec/SpecSSAFs/{InvoiceID} |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| InvoiceID | path | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| SpecSSAFs | form | List<SpecSSAF> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ID | form | int | No | |
| INV_ID | form | int | No | |
| SSAF_N | form | string | No | |
| SSAF_DATE | form | DateTime? | 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 /RS/Spec/SpecSSAFs HTTP/1.1 Host: 10.10.0.107 Accept: application/json
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"}},"SpecSSAFs":[{"ID":0,"INV_ID":0,"SSAF_N":"String","SSAF_DATE":"\/Date(-62135596800000-0000)\/"}]}