Notify/remind all pending signers in a package
Monday, June 22, 2026 at 04:07pmHi OneSpan Team,
I’m working on an integration for OneSpan Sign and need to confirm available API capabilities for signer reminders.
Requirement
- We have a package/transaction with multiple signers.
- We need to trigger reminder notifications from our application for multiple signers in one user action.
- Preferred behavior: provide only packageId (or package + list of signers) and have OneSpan send reminders to all eligible/pending signers in one API call.
What we found so far
- Single signer notification API:
- POST /api/packages/{packageId}/roles/{roleId}/notifications
- Works per signer (roleId), one call at a time.
- Reminder schedule APIs (/api/packages/{packageId}/reminders) appear to be scheduled/automated reminders, not an immediate one-time “notify all now” endpoint.
Questions for confirmation
- Does OneSpan provide any API to immediately notify all pending/incomplete signers of a package in a single call?
- Does OneSpan provide any API to immediately notify a list of signer roleIds in a single call (bulk notify)?
- If neither exists, is the recommended approach to call POST /api/packages/{packageId}/roles/{roleId}/notifications once per signer?
- 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?
Thanks in advance - this confirmation will help us finalize our integration design.
Reply to: Notify/remind all pending signers in a package
Thursday, July 2, 2026 at 08:08amHello 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
Reply to: Notify/remind all pending signers in a package
Thursday, July 2, 2026 at 09:05amHi 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:
This confirmation will help us decide between per-signer notification calls vs reminder-schedule-based flow.
Thanks!
Reply to: Notify/remind all pending signers in a package
Friday, July 10, 2026 at 07:31amHello Vanitha,
Thank you for your follow-up questions.
Notifications are sent immediately. If you trigger a notification (via the UI or API) for a signer, they will receive it right away. If a signer has already completed their signing actions and a notification is subsequently triggered for them, they will still receive that notification.
Reminders, on the other hand, are sent according to the schedule configured by the sender. Reminder schedules can be configured or modified after the transaction has been sent. Please refer to the following documentation for additional details:
Reminders can be configured to be sent no earlier than 1 day after the initial invitation email is sent, and can be scheduled further out depending on the configured reminder settings.
To address your specific questions:
1. If we create/update a reminder schedule after the package is created, will OneSpan send reminders at the next scheduler run to all pending signers for that package?
A. Yes. Reminders will be sent to the pending signers according to the configured reminder schedule.
2. Is this behavior officially supported/recommended for “notify now”-type use cases, or only for recurring scheduled reminders?
A. Reminder schedules are scheduled reminder notifications. Depending on your requirement for immediate notification or scheduled reminders, you may choose.
3. Is there any minimum delay/cadence constraint that prevents near-immediate reminder dispatch?
A. Yes. The earliest a reminder can be sent is 1 calendar day after the initial invitation email. The first reminder can be configured anywhere between 1 and 1000 calendar days after the invitation is sent.
4. Are completed signers always excluded from reminder schedule notifications (including schedules created/updated after the package is already SENT)?
A. Yes. Reminder emails are sent only to recipients who still have pending signing actions.
5. Are there any side effects (duplicate reminders, template differences, throttling, or rate limits) we should account for if we use this pattern?
A. There should not be any side effects associated with configuring reminder schedules as described. Reminders will be processed according to the schedule and sent only to recipients with pending signatures.
Additionally, we recommend thoroughly testing the configuration in your Sandbox environment before implementing any changes in Production. If you need assistance with creating a Sandbox account, please email our Support Team.
Thank you