foods.search/food.get return code 101 "API was not resolved" — Premier Free, IP correctly whitelisted

[kenric regan]

Hi — running into the same issue as this recent thread, where the fix turned out to be enabling specific methods on the API key server-side.

Account: ken...@gmail.com (Premier Free) Client ID / Consumer Key: a171a8e94d8a482f8242c43d7a52cbbb

Every call to foods.search (and presumably food.get) returns HTTP 200 with:

<error> <code>101</code> <message>API was not resolved</message> </error>

Already verified on our end:

• OAuth2 client-credentials token requests succeed and return a valid access token
• Request is POST https://platform.fatsecret.com/rest/server.api with method=foods.search&search_expression=...&format=json, scope=basic
• Our outbound IP is correctly listed under IP Restrictions and matches what's making the requests
• Client ID in our app matches the dashboard

Given the thread above resolved with a staff member manually enabling specific methods on the key, could you confirm whether foods.search/food.get are actually enabled for this Client ID? Happy to provide any other details needed.

Thanks!

[seba...@fatsecret.com]

Hi Ken,
Thanks for following up. As explained via email just now, your account is fully provisioned, there seems to be an error in your OAuth2.0 configuration. Please try using Postman first while you can simply leave scopes blank