Notify/remind all pending signers in a package

Hello Vanitha,

Thank you for the question.

Please find the answers below:

1. Does OneSpan provide any API to immediately notify all pending/incomplete signers of a package in a single call?
A. At this point, we don't have a single call to notify all pending/incomplete signers.

2. Does OneSpan provide any API to immediately notify a list of signer roleIds in a single call (bulk notify)?
A. No.

3. If neither exists, is the recommended approach to call POST /api/packages/{packageId}/roles/{roleId}/notifications once per signer?
recommended
A. You may create a script to run batch API calls to notify the signers. Please note that with this call, even the signer who has completed their signature will receive an email notification if a POST call is made for that signer. Taking that into consideration, you may set up a reminder schedule for the account or at the transaction level

4. For POST/PUT /api/packages/{packageId}/reminders, are reminder emails sent only to signers with pending actions, or to all signers in the package, including already completed signers?
A. Reminders will only be sent to the signers with pending actions. 

Also, we have 2 different email templates that handle this :
1. email.notify - When a notification is either manually triggered or via API [POST /api/packages/{packageId}/roles/{roleId}/notifications]
2. email.remind.signer - When a signer is automatically notified about the pending signatures as per the reminder set.
 

Please let us know if you have any questions for us.

Thank you
 

Hi OneSpan Team,

Thank you for your response. We need one additional clarification to finalize our design.

If we need a user-triggered action to notify all pending signers for a package, can we use the reminder schedule APIs (POST/PUT /api/packages/{packageId}/reminders) as an immediate substitute for bulk notify?

Specifically, can you confirm:

1. If we create/update a reminder schedule after package is created, will OneSpan send reminders at the next scheduler run to all pending signers for that package?
2. Is this behavior officially supported/recommended for “notify now”-type use cases, or only for recurring scheduled reminders?
3. Is there any minimum delay/cadence constraint that prevents near-immediate reminder dispatch?
4. Are completed signers always excluded from reminder schedule notifications (including schedules created/updated after package is already SENT)?
5. Are there any side effects (duplicate reminders, template differences, throttling/rate limits) we should account for if we use this pattern?

This confirmation will help us decide between per-signer notification calls vs reminder-schedule-based flow.

Thanks!