customer-follow-notifications
Operations addressed under /customer-follow-notifications — 7 operations.
get-customer-follow-notification-list
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Response body, read from the service source
The route declares its response as IEnumerable<CustomerFollowNotificationDto>.
| Field | Declared type | Nullable |
|---|---|---|
Id | Guid | no |
CustomerFollowId | Guid | no |
FollowTypeNotificationId | Guid | no |
Member names are the service's declaration names.
query Parameters
orderByorderSortpageIndexpageSizeget-customer-follow-notification-list › Responses
Success. Returns a collection of records. Of 135 operations in this state that were probed (measured against a reference deployment on parameterless GET routes only), 118 answered and 118 returned a bare JSON array.
Array of catalog-declared response records.
customerFollowIdfollowTypeNotificationIdidcreate-customer-follow-notification
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Response body, read from the service source
The route declares its response as AuraCommandDto.
| Field | Declared type | Nullable |
|---|---|---|
Id | Guid | no |
Member names are the service's declaration names.
Error codes this operation is known to raise
| Code | Status | Meaning | Message |
|---|---|---|---|
ERR_LGLFLLW_8 | 400 | FOLLOWTYPE_NOTIFICATION_NOT_FOUND | Follow Type - information cannot be found. Notification:{0} |
ERR_LGLFLLW_9 | 400 | CUSTOMER_FOLLOW_NOT_FOUND | Customer follow cannot be found. :{0} |
create-customer-follow-notification › Request Body
customerFollowIdfollowTypeNotificationIdcreate-customer-follow-notification › Responses
Success. An exact, uniquely bound route registration classifies this response as a single-record.
update-customer-follow-notification
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Error codes this operation is known to raise
| Code | Status | Meaning | Message |
|---|---|---|---|
ERR_LGLFLLW_20 | 400 | CUSTOMER_FOLLOW_NOTIFICATION_NOT_FOUND | Customer follow notification is not found. Id:{0} |
ERR_LGLFLLW_8 | 400 | FOLLOWTYPE_NOTIFICATION_NOT_FOUND | Follow Type - information cannot be found. Notification:{0} |
ERR_LGLFLLW_9 | 400 | CUSTOMER_FOLLOW_NOT_FOUND | Customer follow cannot be found. :{0} |
path Parameters
idupdate-customer-follow-notification › Request Body
customerFollowIdfollowTypeNotificationIdupdate-customer-follow-notification › Responses
Success. The catalog declares no response fields for this operation. The body is UNKNOWN CONTENT. The response type this route registers was read from the service's own source and is published on this operation as x-aura-code-response.
get-customer-follow-notification-call-list
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Response body, read from the service source
The route declares its response as IEnumerable<CustomerFollowNotificationCallDto>.
| Field | Declared type | Nullable |
|---|---|---|
IsReached | bool | no |
IsPromisedPayment | bool | no |
Callid | string | no |
CallDate | DateTime? | yes |
Description | string | no |
PromisedPaymentDate | DateOnly? | yes |
CustomerFollowNotificationId | Guid | no |
Member names are the service's declaration names.
Error codes this operation is known to raise
| Code | Status | Meaning | Message |
|---|---|---|---|
ERR_LGLFLLW_20 | 400 | CUSTOMER_FOLLOW_NOTIFICATION_NOT_FOUND | Customer follow notification is not found. Id:{0} |
path Parameters
idquery Parameters
orderByorderSortpageIndexpageSizeget-customer-follow-notification-call-list › Responses
Success. Returns a collection of records. Of 135 operations in this state that were probed (measured against a reference deployment on parameterless GET routes only), 118 answered and 118 returned a bare JSON array.
Array of catalog-declared response records.
callDatecallIdcallidcustomerFollowNotificationIddescriptionidisPromisedPaymentisReachedpromisedPaymentDatecreate-customer-follow-notification-call
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Response body, read from the service source
The route declares its response as AuraCommandDto.
| Field | Declared type | Nullable |
|---|---|---|
Id | Guid | no |
Member names are the service's declaration names.
Error codes this operation is known to raise
| Code | Status | Meaning | Message |
|---|---|---|---|
ERR_LGLFLLW_12 | 400 | CALL_ID_ALREADY_REGISTERED | A notification has been registered for this callid before. Call:{0} |
ERR_LGLFLLW_20 | 400 | CUSTOMER_FOLLOW_NOTIFICATION_NOT_FOUND | Customer follow notification is not found. Id:{0} |
path Parameters
idcreate-customer-follow-notification-call › Request Body
callDatecallIddescriptionisPromisedPaymentisReachedpromisedPaymentDatecreate-customer-follow-notification-call › Responses
Success. An exact, uniquely bound route registration classifies this response as a single-record.
get-customer-follow-notification-sms-list
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Response body, read from the service source
The route declares its response as IEnumerable<CustomerFollowNotificationSmsDto>.
| Field | Declared type | Nullable |
|---|---|---|
SmsNotificationId | Guid? | yes |
NotificationDate | DateTime? | yes |
CustomerFollowNotificationId | Guid | no |
Member names are the service's declaration names.
Error codes this operation is known to raise
| Code | Status | Meaning | Message |
|---|---|---|---|
ERR_LGLFLLW_20 | 400 | CUSTOMER_FOLLOW_NOTIFICATION_NOT_FOUND | Customer follow notification is not found. Id:{0} |
path Parameters
idquery Parameters
orderByorderSortpageIndexpageSizeget-customer-follow-notification-sms-list › Responses
Success. Returns a collection of records. Of 135 operations in this state that were probed (measured against a reference deployment on parameterless GET routes only), 118 answered and 118 returned a bare JSON array.
Array of catalog-declared response records.
customerFollowNotificationIdidnotificationDatesmsNotificationIdcreate-customer-follow-notification-sms
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Response body, read from the service source
The route declares its response as AuraCommandDto.
| Field | Declared type | Nullable |
|---|---|---|
Id | Guid | no |
Member names are the service's declaration names.
Error codes this operation is known to raise
| Code | Status | Meaning | Message |
|---|---|---|---|
ERR_LGLFLLW_20 | 400 | CUSTOMER_FOLLOW_NOTIFICATION_NOT_FOUND | Customer follow notification is not found. Id:{0} |
path Parameters
idcreate-customer-follow-notification-sms › Request Body
notificationDatesmsNotificationIdcreate-customer-follow-notification-sms › Responses
Success. An exact, uniquely bound route registration classifies this response as a single-record.