Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the powerful-docs domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/spectra-qa-sites/webapps/sureforms-staging-qa/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the convertpro-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/spectra-qa-sites/webapps/sureforms-staging-qa/wp-includes/functions.php on line 6131

Notice: Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see Debugging in WordPress for more information. (This message was added in version 5.7.0.) in /home/spectra-qa-sites/webapps/sureforms-staging-qa/wp-includes/functions.php on line 6131
API Request Failed - Nonce Verification Error - SureForms
|
/ Documentation /Troubleshooting/ API Request Failed – Nonce Verification Error

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:

  1. 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.
  2. Resubmit the Form:  Once the trigger is re-initialized, submit the form again. This will generate a fresh nonce.
  3. 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.

Need help? Contact Support
On this page
Scroll to Top