New Power-Up API key and token consistently return 401 on /1/members/me

Trello
1

Hello,

I am trying to integrate a local editorial calendar with Trello through the REST API.

Steps taken:

  1. Created a new Power-Up in the Power-Up Admin Portal, with a valid HTTPS iframe connector and contact information.
  2. Generated a new API key.
  3. Authorized the app from /1/authorize with expiration=never, scope=read,write, and response_type=token.
  4. Confirmed that the authorized application is listed in the Trello account settings and never expires.
  5. Requested GET https://api.trello.com/1/members/me.

Result: HTTP 401 (“invalid key”) consistently.

I tested both supported authorization methods:

  • query string authentication (?key=…&token=…);
  • Authorization header: OAuth oauth_consumer_key=“…”, oauth_token=“…”.

I also revoked the token, generated a new one, deleted the original Power-Up, recreated it with a new API key and token, and retried after more than 30 minutes. The result remained 401.

No API key or token is included here.

Is there any additional activation, approval, or configuration required for a newly created Power-Up API key to work with the REST API? Is there a known issue with newly generated keys/tokens?

Thank you.