Back to all discussions

  •   about 2 months ago

Token Vault Connected Accounts - My Account API returns 404

I'm building a Python/FastAPI project using Token Vault with Connected Accounts. I've configured my Google social connection with the purpose set to "Authentication and Connected Accounts for Token Vault" and enabled the Token Vault grant type on my application.

When I try to initiate the Connected Accounts flow by calling POST to https://{my-domain}/me/v1/connected-accounts, I get a 404 Not Found error:
{"title":"Not Found","type":"https://auth0.com/api-errors/A0E-404-0001","detail":"The requested resource POST /me/v1/connected-accounts was not found.","status":404}

I've activated the My Account API under Applications → APIs, authorized my app with connected_accounts scopes, and I'm passing a valid access token with the My Account API audience. I'm on the free tier.

Is there an additional step needed to enable the Connected Accounts endpoint? The docs mention it's in Limited Early Access - is it available for hackathon participants? Any help would be appreciated. Thanks!

P.S. - The Discord link on the hackathon discussion page seems to be expired/invalid and I haven't been able to join. If anyone has an updated invite link, could you please share it? Thanks again!

  • 4 comments

  • Manager   •   about 2 months ago

    You should be able to connect to discord with this link: https://discord.gg/vSCJgPGK. Let me know if you can't connect to the server. I will have to come back and look at this.

  • Manager   •   about 2 months ago

    Gautam Ronanki can you re-post on the discord server in #ask-organizers?

    https://discord.gg/vSCJgPGK.

    it will be easier to discuss and share screenshots when applicable.

    It's also worth double-checking the endpoint you are using to initiate the connected accounts flow. You have

    /me/v1/connected-accounts

    but it may need to be /me/v1/connected-accounts/connect

  •   •   about 2 months ago

    Thanks, Fred! It worked like a charm. The /connected-accounts/connect endpoint was correct, which fixed the 404. I also needed to set up a Multi-Resource Refresh Token (MRRT) to exchange my refresh token for a My Account API access token before calling the endpoint. Everything is working now.

  • Manager   •   about 2 months ago

    Awesome, great to hear, Gautam!

Log in or sign up for Devpost to join the conversation.