Ghost Admin API: create members

Feature Requests
21

Can you please share your workflow to see If I can spot the issue?

22

Alright, here it goes

23

Noticed that you have an extra $ in the authorization header: Ghost ${{$json["token"]}}. Remove that extra $ and try again.

24

Good day to you Ricardo,

that was on purpose, because the alternative returns this error:

ERROR: UNKNOWN ERROR - check the detailed error for more information
Invalid token: jwt audience invalid. expected: /\/?canary\/admin\/?$/

full


"status": "rejected",
"reason": {
"name": "StatusCodeError",
"statusCode": 401,
"message": "401 - {"errors":[{"message":"Invalid token: jwt audience invalid. expected: /\\/?canary\\/admin\\/?$/","context":null,"type":"UnauthorizedError","details":null,"property":null,"help":null,"code":"INVALID_JWT","id":"7696d5b0-4dc7-11ec-a4b0-312aea5f6t7z"}]}",
"error": {
"errors": [
{
"message": "Invalid token: jwt audience invalid. expected: /\/?canary\/admin\/?$/",
"context": null,
"type": "UnauthorizedError",
"details": null,
"property": null,
"help": null,
"code": "INVALID_JWT",
"id": "7696d5b0-4dc7-11ec-a4b0-312aea5f6t7z"
}
]
},

might be then that the JWT token generation flow needs another adjustment.

25

Hey there Ricardo, sorry for pinging, do you think the error is in the token generation node?

26

Somehow missed your last message. Sorry about that.

It looks like since the endpoint it’s experimental, the audience should be /canary/admin/ instead of /${version}/admin/. Try it like that, and let me know if that works.

2 Likes
27

Perfect Ricardo, this does the trick! <3

1 Like
28

Great that it worked. Have fun.

1 Like