Title: API Token Issues
Last modified: April 4, 2023

---

# API Token Issues

 *  Resolved [StarryMom](https://wordpress.org/support/users/starrymom/)
 * (@starrymom)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/)
 * When I add my API token and save settings, it won’t pull my kit and I get the
   following message:
 * _Token Validation: Please add your API token above. Save settings to validate
   token. Token successfully validated. Could not validate token. Please verify 
   the token has been correctly entered._
 * I generated a new token, that didn’t work. Uninstalled, deleted, reinstalled 
   plugin, that didn’t work either.
 * How can we resolve this?

Viewing 10 replies - 1 through 10 (of 10 total)

 *  Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * (@mattkeys)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/#post-16623688)
 * Those are _all_ of the possible token validation messages being seen at once.
   The correct one is supposed to be displayed using javascript. The fact that you
   are seeing them all at once would mean that one of a couple things are happening.
    1. The JS assets for this plugin are not loading successfully for some reason
    2. There is a JS error on the page preventing further script execution
 * If you are familiar with your browsers developer tools/console you may be able
   to help diagnose which of the two issues is happening. Are there any errors in
   the console? Either JS errors, or perhaps a 404 when it tries to load the JS 
   asset?
    -  This reply was modified 3 years, 1 month ago by [Matt Keys](https://wordpress.org/support/users/mattkeys/).
 *  Thread Starter [StarryMom](https://wordpress.org/support/users/starrymom/)
 * (@starrymom)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/#post-16623716)
 * Checked in Chrome and Firefox
 * No errors, no 404s in console.
 * Disabled all plugins except for ACF and ACF FA. Used default theme. Same issue.
 *  Thread Starter [StarryMom](https://wordpress.org/support/users/starrymom/)
 * (@starrymom)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/#post-16623748)
 * Tested on local. Fresh install. Only installed ACF Pro and ACF FA. Before doing
   anything besides activating the plugins, I get that same message:
 * Token Validation: Please add your API token above. Save settings to validate 
   token. Token successfully validated. Could not validate token. Please verify 
   the token has been correctly entered.
 *  Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * (@mattkeys)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/#post-16625461)
 * Thanks for those tests. Can you tell me if these two plugins are installed normally
   through the WordPress plugin manager, or are they bundled with a theme?
 *  Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * (@mattkeys)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/#post-16626475)
 * FYI i’ve been able to reproduce your issue, I’m looking into it.,
 *  Thread Starter [StarryMom](https://wordpress.org/support/users/starrymom/)
 * (@starrymom)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/#post-16626478)
 * Awesome, thank you for working on the issue!
 *  Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * (@mattkeys)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/#post-16626490)
 * NP. It looks like in ACF the admin menu is now called “ACF” instead of “Custom
   Fields” seems innocent enough but that slug is used in this plugin when determining
   if we are on the correct admin page to enqueue our scripts:
 *     ```wp-block-code
       $acf_menu_slug = sanitize_title( __( 'Custom Fields', 'acf' ) );
       if ( $acf_menu_slug . '_page_fontawesome-settings' != $hook ) {
       	return;
       }
       ```
   
 * I’ll probably need to check for the old and the new page slugs for a while to
   cover people who haven’t updated.
    -  This reply was modified 3 years, 1 month ago by [Matt Keys](https://wordpress.org/support/users/mattkeys/).
 *  Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * (@mattkeys)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/#post-16626603)
 * [@starrymom](https://wordpress.org/support/users/starrymom/) can you check out
   v4.0.5 of this plugin just released and see if it resolves the issue you were
   seeing?
 *  Thread Starter [StarryMom](https://wordpress.org/support/users/starrymom/)
 * (@starrymom)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/#post-16626610)
 * Yes, that fixed it. Thank you, I appreciate it!
 *  Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * (@mattkeys)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/#post-16626614)
 * Wonderful, thanks for reporting the issue.

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘API Token Issues’ is closed to new replies.

 * ![](https://ps.w.org/advanced-custom-fields-font-awesome/assets/icon-256x256.
   jpg?rev=3435775)
 * [Advanced Custom Fields: Font Awesome Field](https://wordpress.org/plugins/advanced-custom-fields-font-awesome/)
 * [Support Threads](https://wordpress.org/support/plugin/advanced-custom-fields-font-awesome/)
 * [Active Topics](https://wordpress.org/support/plugin/advanced-custom-fields-font-awesome/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/advanced-custom-fields-font-awesome/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/advanced-custom-fields-font-awesome/reviews/)

 * 10 replies
 * 2 participants
 * Last reply from: [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * Last activity: [3 years, 1 month ago](https://wordpress.org/support/topic/api-token-issues/#post-16626614)
 * Status: resolved