Title: FontAwesome API Token
Last modified: June 16, 2023

---

# FontAwesome API Token

 *  [huskii](https://wordpress.org/support/users/huskii/)
 * (@huskii)
 * [2 years, 12 months ago](https://wordpress.org/support/topic/fontawesome-api-token/)
 * Hello,
 * At the options page you have the field “FontAwesome API Token” where you can 
   enter your API Token. Is there an function / hook we can use and set in the functions.
   php or wp-config.php to automatically fill in this field?
   We would like to add
   the API Key to our .env file and then define it somewhere like in the wp-config.
   php

Viewing 1 replies (of 1 total)

 *  Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * (@mattkeys)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/fontawesome-api-token/#post-16830902)
 * Hey [@huskii](https://wordpress.org/support/users/huskii/),
 * That isn’t currently an option although I do agree it should be and I’d wager
   it will find it’s way into the next bigger update to this plugin.

Viewing 1 replies (of 1 total)

The topic ‘FontAwesome API Token’ 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/)

## Tags

 * [automation](https://wordpress.org/support/topic-tag/automation/)

 * 1 reply
 * 2 participants
 * Last reply from: [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * Last activity: [2 years, 11 months ago](https://wordpress.org/support/topic/fontawesome-api-token/#post-16830902)
 * Status: not resolved