• Home
  • Categories
  • Recent
  • Popular
  • Pricing
  • Contact us
  • Docs
  • Login
FusionAuth
  • Home
  • Categories
  • Recent
  • Popular
  • Pricing
  • Contact us
  • Docs
  • Login

Retrieve a User by Email Verification Id api NOT WORKING

Scheduled Pinned Locked Moved Solved
Q&A
3
3
4.6k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    arihantverma52
    last edited by 11 Mar 2022, 17:28

    Does this API work for anyone? It's giving me a 404 when I try to use it.
    GET /api/user?verificationId={verificationId}

    Thanks

    D 1 Reply Last reply 12 Mar 2022, 15:49 Reply Quote 0
    • S
      scottbradley
      last edited by 27 Jul 2024, 01:12

      This endpoint returns a 404 for an invalid or expired verificationId. It is also the case that you can only use a verificationId once for verification before it becomes stale.

      What does this mean for your workflow? In my case, I was trying to verify a user's registration in the same request cycle as verifying their email. To do this, I needed to fetch the user response to get the user ID to verify the registration. Naturally, I was doing this after posting the email verification -- the result being said 404.

      So, in terms of workflow, if you need to look up a user by verificationId, be sure to do it before you actually use the ID for verification.

      Let me know if I got any of this wrong @arihantverma52

      1 Reply Last reply Reply Quote 0
      • D
        dan @arihantverma52
        last edited by 12 Mar 2022, 15:49

        @arihantverma52

        Please share your entire request, the version of FusionAuth, any debug logs, and your FusionAuth configuration. Otherwise it is difficult to provide you any assistance.

        --
        FusionAuth - Auth for devs, built by devs.
        https://fusionauth.io

        1 Reply Last reply Reply Quote 0
        • S
          scottbradley
          last edited by 27 Jul 2024, 01:12

          This endpoint returns a 404 for an invalid or expired verificationId. It is also the case that you can only use a verificationId once for verification before it becomes stale.

          What does this mean for your workflow? In my case, I was trying to verify a user's registration in the same request cycle as verifying their email. To do this, I needed to fetch the user response to get the user ID to verify the registration. Naturally, I was doing this after posting the email verification -- the result being said 404.

          So, in terms of workflow, if you need to look up a user by verificationId, be sure to do it before you actually use the ID for verification.

          Let me know if I got any of this wrong @arihantverma52

          1 Reply Last reply Reply Quote 0
          • A Alex Patterson has marked this topic as solved on 6 Aug 2024, 15:00
          • First post
            Last post