Difference between revisions of "API Method EventNotificationBulkCreate"
From Updox API
(→payload) |
(→internalId) |
||
Line 14: | Line 14: | ||
* The content of payload cannot be empty, otherwise the notification will be considered invalid. | * The content of payload cannot be empty, otherwise the notification will be considered invalid. | ||
− | === internalId === | + | ==== internalId ==== |
+ | |||
+ | * This field is here as a way for a requester to track their notifications being created. | ||
=== deliveryDateTime === | === deliveryDateTime === |
Revision as of 17:07, 11 December 2015
Contents |
Description
The following describes the processes involved when sending bulk event notifications.
A bulk event notification consists of a JSON object populated with a list of:
- payload (the content of the notification) - internal id (an identification id specified by the requester) - delivery date/time - delivery method
Field Validations
payload
* The content of payload cannot be empty, otherwise the notification will be considered invalid.
internalId
* This field is here as a way for a requester to track their notifications being created.
deliveryDateTime
deliveryDestination
deliveryMethod
Prerequisites
1 This API call requires Vendor-level credentials. The credentials should be populated into the applicationId
and applicationPassword
fields of the auth
block:
{ ... "auth": { "applicationId": "vendorId", "applicationPassword": "vendorPassword", "accountId": "", "userId": "" } }
2 This API call requires a Practice/Account-level identifier. The identifier should be populated into the accountId
field of the auth
block:
{
...
"auth": {
"applicationId": "vendorId",
"applicationPassword": "vendorPassword",
"accountId": "practiceId",
"userId": ""
}
}