Title: REST API error
Last modified: June 18, 2021

---

# REST API error

 *  Resolved [SocialSparkMedia](https://wordpress.org/support/users/socialsparkmedia/)
 * (@socialsparkmedia)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/rest-api-error-24/)
 * Getting this error when I activate the plugin. I was using it on a staging site
   without problems, now I’ve launched it live and getting this error:
 * Notice: register_rest_route was called incorrectly. The REST API route definition
   for age-gate/v1/shortcode is missing the required permission_callback argument.
   For REST API routes that are intended to be public, use __return_true as the 
   permission callback. Please see Debugging in WordPress for more information. (
   This message was added in version 5.5.0.) in /www/wp-includes/functions.php on
   line 5313
 * Help!

Viewing 1 replies (of 1 total)

 *  Thread Starter [SocialSparkMedia](https://wordpress.org/support/users/socialsparkmedia/)
 * (@socialsparkmedia)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/rest-api-error-24/#post-14572662)
 * It appears this is a conflict with Google’s Site Kit. I will deactivate and use
   code instead. But it would be nice to be able to use that.

Viewing 1 replies (of 1 total)

The topic ‘REST API error’ is closed to new replies.

 * ![](https://ps.w.org/age-gate/assets/icon-256x256.png?rev=2783003)
 * [Age Gate](https://wordpress.org/plugins/age-gate/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/age-gate/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/age-gate/)
 * [Active Topics](https://wordpress.org/support/plugin/age-gate/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/age-gate/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/age-gate/reviews/)

 * 1 reply
 * 1 participant
 * Last reply from: [SocialSparkMedia](https://wordpress.org/support/users/socialsparkmedia/)
 * Last activity: [4 years, 11 months ago](https://wordpress.org/support/topic/rest-api-error-24/#post-14572662)
 * Status: resolved