Source
Signing workflow & signer experience — found from sitemap — OneSpan Sign
Checked for OneSpan Sign on 10 Nov 2026
- Page
- https://docs.onespan.com/docs/bulk-sending
- Checked
- 10 Nov 2026, 08:48 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:992b3cedc8ed0f56adf6bf21d364c86c95f4b0443d322a1fe2e517b964f2d1f7
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Bulk send purpose Report an error
“The Bulk Send feature enables users to create and distribute multiple transactions with minimum effort by using: An eligible template, which will be used to create the transactions.”
-
Bulk send template requirements Report an error
“A template is "eligible" if it has: At least one document other than the Consent Agreement At least one placeholder Role At least one Signature Field (not necessarily for the placeholder Role)”
-
Bulk send max file size Report an error
“The maximum file size is 8 MB.”
-
Bulk send processing capacity Report an error
“A maximum of approximately 3000 transactions are processed per hour.”
-
Bulk send recommended batch Report an error
“for a very large bulk send we recommend that you break your request into smaller batches of 1000 lines per hour.”
-
Bulk send account enabled prerequisite Report an error
“The Bulk Send feature must be enabled on your account.”
-
Bulk send SMS phone format Report an error
“When initiating a Bulk Send using SMS, the phone numbers must follow the E.164 (opens in new tab) format.”
-
Bulk send CSV required fields Report an error
“{PlaceholderRoleName}, FIRST_NAME, LAST_NAME, and EMAIL are required fields. All others are optional.”
-
Bulk send field population Report an error
“A FieldId is the ID of a field that belongs to a placeholder Role. It can be used to automatically populate that field in your documents. The header row can have as many of those fields as you need.”
-
Bulk send signer verification support Report an error
“If you want to specify a method of External Signer Verification (SIGNER_VERIFICATION) such as PCC or DIGIPASS, please contact our Support Team”
-
Bulk send multiple placeholders Report an error
“If your transactions contain more than one placeholder Role, you must append a set of header fields for each additional role. All required fields must be present for each placeholder Role.”
-
Bulk send encoding non ascii Report an error
“If the data you need to put in the CSV file contains non-ASCII characters (e.g., accented characters, Chinese characters), the CSV file should be saved with UNICODE UTF-8 encoding.”
-
Bulk send validation header first Report an error
“OneSpan Sign validates the header row before validating any other row in a CSV file.”
-
Bulk send auth types Report an error
“The value assigned to AUTH_TYPE must be NONE, CHALLENGE, SSO, or SMS.”
-
Bulk send challenge validation Report an error
“At least one AUTH_PROMPT/AUTH_CHALLENGE pair has been specified. There is a 1:1 mapping between prompts and challenges (i.e., for every prompt, there is a challenge — and vice versa).”
-
Bulk send SMS validation Report an error
“If AUTH_TYPE = SMS for a particular Role, OneSpan Sign verifies that for that Role there is at least one prompt. The verification process will examine only the first prompt, which should be used to specify the phone number to which an SMS message will be sent.”
-
Bulk send scheduling Report an error
“Bulk Send transactions are placed in a queue. Every 15 minutes, the queue is checked. If new Bulk Send jobs have arrived, they are processed in order until the queue is empty.”
-
Bulk send signing method ID Report an error
“The CSV file must specify the ID of the signing method. That ID is case-sensitive. For the method Signing with a Certificate, that ID is "personalCertificateSigning".”
-
Bulk send API trigger Report an error
“Attempting to trigger a Bulk Send from the API for a template with an unsupported language will throw an error.”
Scores citing this record
- The Data Protection Officer eIDAS levels & trust services
- The Data Protection Officer Signer identification
- The Data Protection Officer Signing workflow & signer experience
- The HR Operations Lead Signer identification
- The HR Operations Lead Signing workflow & signer experience
- The Integration Engineer eIDAS levels & trust services
- The Integration Engineer Signer identification
- The Integration Engineer Signing workflow & signer experience
- The Integration Engineer Integrations & API
- The Integration Engineer Pricing transparency
- The Legal Counsel Signer identification
- The Legal Counsel Signing workflow & signer experience
- The Legal Counsel Integrations & API
- The Legal Counsel Pricing transparency
- The Revenue Operations Lead Signer identification
- The Revenue Operations Lead Signing workflow & signer experience
- The Revenue Operations Lead Pricing transparency
- The Skeptic Signer identification
- The Skeptic Signing workflow & signer experience
- The Skeptic Pricing transparency