POST | /business-entities/{BeeNumber}/tax-trans |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
BeeNumber | path | decimal? | No | |
TransactionDate | body | DateTime | No | |
CodeIdFed1099Boxes | body | string | No | |
TransactionAmount | body | decimal | No | |
TransactionSource | body | string | No | |
TaxTransReference | body | string | No | |
Memo | body | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ResponseStatus | form | ResponseStatus | No | |
BeeTaxTransGuid | form | decimal? | 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 /business-entities/{BeeNumber}/tax-trans HTTP/1.1
Host: extensions.avon.ca
Accept: application/json
Content-Type: application/json
Content-Length: length
{"beeNumber":0,"transactionDate":"0001-01-01T00:00:00.0000000","codeIdFed1099Boxes":"String","transactionAmount":0,"transactionSource":"String","taxTransReference":"String","memo":"String"}
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"}},"beeTaxTransGuid":0}