QBO Webhooks Listener

QboWebhooksRequest

The following routes are available for this service:
POST	/qbowebhook

**QboWebhooksRequest** Parameters:
Name	Parameter	Data Type	Required	Description
EventNotifications	body	List<QBOEventNotification>	No

**QBOEventNotification** Parameters:
Name	Parameter	Data Type	Required	Description
RealmId	form	string	No
DataChangeEvent	form	QBODataChangeEvent	No

**QBODataChangeEvent** Parameters:
Name	Parameter	Data Type	Required	Description
Entities	form	List<QBOEntity>	No

**QBOEntity** Parameters:
Name	Parameter	Data Type	Required
Name	form	QBOEntityName	No
Id	form	string	No
Operation	form	QBOOperation	No
LastUpdated	form	DateTime	No
DeletedId	form	string	No

**QBOEntityName** Enum:
Name	Value
Customer	20
Department	21
Vendor	21
Deposit	22
Invoice	23
Bill	24
Item	24
JournalCode	25
PurchaseOrder	25
JournalEntry	26
Estimate	26
RefundReceipt	26
Employee	27
SalesReceipt	27
TaxAgency	28
Term	29
TimeActivity	30
Account	30
Transfer	31
VendorCredit	31
CreditMemo	32
Purchase	33
Currency	33
Payment	35
PaymentMethod	36
BillPayment	36
Preferences	37
Budget	37
Class	38

**QBOOperation** Enum:
Update
Create
Merge
Delete
Emailed
Void

To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv

HTTP + JSV

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

POST /qbowebhook HTTP/1.1 
Host: wh.entersecurity.com 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	eventNotifications: 
	[
		{
			realmId: String,
			dataChangeEvent: 
			{
				entities: 
				[
					{
						name: Customer,
						id: String,
						operation: Update,
						lastUpdated: 0001-01-01,
						deletedId: String
					}
				]
			}
		}
	]
}

HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

(string)