Title: API Returning Error
Last modified: September 20, 2021

---

# API Returning Error

 *  Resolved [europoint](https://wordpress.org/support/users/europoint/)
 * (@europoint)
 * [4 years, 8 months ago](https://wordpress.org/support/topic/api-returning-error/)
 * Using standard OMGF, When I select the Save and Optimise button, I get an API
   error, e.g.
    “Open Sans could not be found. The API returned the following error:”
   followed by an error page from Heroku stating “Application Error”.
 * I can’t tell whether this is an error with the API (I did try a direct API call
   for the font and got the same error), or if I need to make any changes to my 
   CSP to permit this to work.
 * Any ideas?

Viewing 1 replies (of 1 total)

 *  Plugin Author [Daan van den Bergh](https://wordpress.org/support/users/daanvandenbergh/)
 * (@daanvandenbergh)
 * [4 years, 8 months ago](https://wordpress.org/support/topic/api-returning-error/#post-14881890)
 * If you’re seeing an Heroku error then there’s an error with the API. They seem
   to be having these a lot lately.
 * I suggest you try again later.

Viewing 1 replies (of 1 total)

The topic ‘API Returning Error’ is closed to new replies.

 * ![](https://ps.w.org/host-webfonts-local/assets/icon-256x256.png?rev=3300821)
 * [OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.](https://wordpress.org/plugins/host-webfonts-local/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/host-webfonts-local/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/host-webfonts-local/)
 * [Active Topics](https://wordpress.org/support/plugin/host-webfonts-local/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/host-webfonts-local/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/host-webfonts-local/reviews/)

 * 1 reply
 * 4 participants
 * Last reply from: [Daan van den Bergh](https://wordpress.org/support/users/daanvandenbergh/)
 * Last activity: [4 years, 8 months ago](https://wordpress.org/support/topic/api-returning-error/#post-14881890)
 * Status: resolved