NAV

BusinessEntityDocumentCreate

EntityAPI|BusinessEntityDocument

The following routes are available for this service:
POST	/business-entities/{BeeNumber}/documents

**BusinessEntityDocumentCreate** Parameters:
Name	Parameter	Data Type	Required
BeeNumber	path	decimal?	Yes
DocumentCategoryId	body	string	Yes
DocumentName	body	string	Yes
UserName	body	string	No
CreatedDate	body	DateTime	Yes
DocumentDefinition	body	string	No
OverwriteIfExists	body	bool	No

**BusinessEntityDocumentCreateResponse** Parameters:
Name	Parameter	Data Type	Required	Description
BeeDocumentGuid	form	long	No

**CreateResponse** Parameters:
Name	Parameter	Data Type	Required	Description
ResponseStatus	form	ResponseStatus	No
Links	form	HateoasLinks	No

**HateoasLink** Parameters:
Name	Parameter	Data Type	Required
Rel	form	string	No
Href	form	string	No
Type	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

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /business-entities/{BeeNumber}/documents HTTP/1.1 
Host: extensions.avon.ca 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"beeNumber":0,"documentCategoryId":"String","documentName":"String","userName":"String","createdDate":"0001-01-01T00:00:00.0000000","documentDefinition":"String","overwriteIfExists":false}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"beeDocumentGuid":0,"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}},"links":[{"rel":"String","href":"String","type":"String"}]}