delightful-vase-86107
04/16/2023, 9:18 AMBearer
$ curl <https://growthbook-api.example.com/feature/sample_feature_name> -H "Authorization: Bearer secret_xxxxxxxxxxxxxxxxxxxxxxxxx"
{
"status": 401,
"message": "jwt malformed"
}
using basicAuth
$ curl <https://growthbook-api.example.com/feature/sample_feature_name> -u secret_xxxxxxxxxxxxxxxxxxxxxxxxx:
{
"status": 401,
"message": "Format is Authorization: Bearer [token]"
}
any ideas?fresh-football-47124
better-magician-65629
04/18/2023, 9:32 PM/api/v1
assuming you're trying to use this endpoint: https://docs.growthbook.io/api/#tag/features/operation/getFeature<https://growthbook-api.example.com/feature/sample_feature_name>
use:
<https://growthbook-api.example.com/api/v1/features/sample_feature_name>
note that feature
needs to be features
.delightful-vase-86107
04/19/2023, 8:59 AMsteep-dawn-35762
04/19/2023, 9:13 AMisQaMode
and forcedVariationsMap
, but I don't understand how our QA team would toggle those on a per test basis.
Perhaps we'd be better off using the feature toggle endpoint as described above?
Thanks!better-magician-65629
04/19/2023, 6:55 PMencodeURIComponent
.. or encode URLs another way.
what you could do is in your staging or QA environment, set .allowUrlOverrides(true)
but use .allowUrlOverrides(false)
in production (unless you're comfortable with tech savvy users enabling features for themselves).