- Calculation Formula Guide
- Using Calculations in SureForms: A Step-by-Step Guide
- GDPR Compliant Forms
- Conversational Form
- Instant Forms
- Create Multi Step Forms In WordPress
- Create WordPress Forms With Conditional Logic
- How to Create Inline Forms in SureForms
- SureForms Login Block – Step-by-Step Guide
- SureForms Registration Block – Step-by-Step Guide
- Unable to Upload SureForms ZIP: File Unzipped On Download
- Browser Support for SureForms
- Not Getting Update Notifications
- How To Rollback to Previous SureForms Versions
- Publishing Failed: Invalid JSON Response
- Troubleshooting Email Sending In SureForms
- SureForm Submissions Marked as Spam
- API Request Failed – Nonce Verification Error
- Fixing the “Destination folder already exists” Error When Installing SureForms
- srfm_enable_redirect_activation
- sureforms_plugin_action_links
- srfm_quick_sidebar_allowed_blocks
- srfm_integrated_plugins
- srfm_suretriggers_integration_data_filter
- srfm_form_submit_response
- srfm_enable_gutenberg_post_types
- srfm_languages_directory
- srfm_form_template
- srfm_disable_nps_survey
API Request Failed – Nonce Verification Error
Error Message:
There was an error(s) with your Workflow.
API request failed: { “code”:”SRFM_NONCE_VERIFICATION_FAILED”,”message”:”Nonce verification failed.”,”data”:null }
What This Means:
This error occurs when the security token (called a nonce) used during the form submission process has expired or is no longer valid. This is intentional and is a standard security feature in WordPress to ensure each request is unique and protected from misuse.
How to Fix:
To resolve this error, follow these steps to reset the nonce:
- Re-initialize the SureForms and OttoKit: Go back to your workflow and reconfigure the SureForms OttoKit step. This refreshes the nonce and prepares the workflow to accept new data securely.
- Resubmit the Form: Once the trigger is re-initialized, submit the form again. This will generate a fresh nonce.
- Proceed to configure the SureForms Action: Now you can continue to set up your SureForms Action as usual, and the error should no longer appear.
Was this doc helpful?
What went wrong?
We don't respond to the article feedback, we use it to improve our support content.
On this page