• Resolved evans44

    (@evans44)


    Our IT group here at Purdue University has stated that they “block access to the API from off-campus but if I can provide a secure endpoint URL we can allow access for that plugin.? We are not able to allow the entire WordPress API due to security issues”. I can not upload the WordPress Rest API but they are sharing that if I can get the API secure endpoint URL then they can allow access so that the plugin can communicate with that endpoint. The IT team shared that it should be in the instructions or somewhere in the plugin upload info. I am not finding this url, for ex: https://<site -url>/wp-json/v2/AIOSEO/, something that looks like that. If you can provide this url I would appreciate it. We do not have the Pro but it looks like that would not help with this issue due to the set up Purdue has for their secure WordPress server. Thank you!

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Prabhat

    (@prabhatrai)

    Hey @evans44,

    Thanks for reaching out

    You can ask the IT team to allow all the URLs under /wp-json/aioseo/ or https://www.purdue.edu/fnr/extension/wp-json/aioseo/*

    This would whitelist all the endpoints of All in One SEO.

    Please let me know if you have any questions or need any help.

    Thanks!

    Thread Starter evans44

    (@evans44)

    Thank you for your quick response! I have sent this info to Purdue IT. If we have any other questions I can follow up. Thank you again!

    Thread Starter evans44

    (@evans44)

    Quick question: do we have to have the Pro version to allow the API/url to work? I just wanted to see if there were any suggestions to enabling the feature without the pro to allow it to work. Have to ask, thanks.

    Plugin Support Prabhat

    (@prabhatrai)

    Hey?@evans44,

    You won’t need our Pro version to whitelist the URL. You can simply ask the IT team to whitelist the path I shared in my previous reply.

    Feel free to let me know if you have any questions.

    Thanks!

    Thread Starter evans44

    (@evans44)

    Prabhat,
    There are settings in the plugin that states you have to have pro to use the API. See attached.

    This is what our IT staff member shared after he saw your response below:
    “So technically, you wouldn’t need the pro version for us to whitelist the URL but it seems that the API piece for the plugin needs it to be used with the endpoint.? It’s not clear if you can use the API without having it enabled with the pro version for the plugin.? Also, we would need the API enabled for the plugin to see if it is secure before we can allow the URL.? Are you able to send them the screenshot that you sent to me?? Maybe that will help them understand what we need clarification on.”
    Derrick
    Purdue IT

    Thank you for your help on this as we are not sure how to move forward with the settings stating to enable it you have to have Pro.
    Diana
    Purdue Forestry and Natural Resources

    Plugin Support Prabhat

    (@prabhatrai)

    Hi @evans44,

    The OpenAI API Key is completely different from the WordPress REST API. In our Pro version, we have OpenAI integration which automatically generates SEO Title & Meta Description suggestions for your website –

    https://aioseo.com/docs/using-openai-to-generate-seo-titles-and-meta-descriptions/

    On the other hand, the WordPress REST API is a common way for plugins to connect to and communicate with WordPress. Both our Free and Pro version uses the WordPress REST API to communicate with WordPress –

    https://aioseo.com/docs/aioseo-uses-rest-api/

    The OpenAI integration is a feature of our Pro version. If you want to use this feature, you can upgrade to our Pro version. However, as mentioned in my previous reply, you don’t need to have the Pro version to whitelist the REST API path for All in One SEO.

    Could you confirm with your IT team if the REST API issue is fixed and if the path for All in One SEO is whitelisted?

    I’m looking forward to hearing back from you.

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘API Secure Endpoint’ is closed to new replies.