# MFA - Including authenticator id in response of POST /mfa/associate

**URL:** <https://community.auth0.com/t/mfa-including-authenticator-id-in-response-of-post-mfa-associate/186659>\
**Category:** Product Feedback\
**Tags:** authentication\_api, mfa-enrollments, api\
**Created:** [May 13, 2025, 10:05am UTC](https://community.auth0.com/t/mfa-including-authenticator-id-in-response-of-post-mfa-associate/186659 "2025-05-13T10:05:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![t.stratmann](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/t.stratmann/32/71238_2.png) [@t.stratmann](https://community.auth0.com/u/t.stratmann)\
**Post date:** [May 13, 2025, 10:05am UTC](https://community.auth0.com/t/mfa-including-authenticator-id-in-response-of-post-mfa-associate/186659/1 "2025-05-13T10:05:27Z")

</div>

**Feature:** Adding authenticator id of MFA enrollment to response of POST /mfa/associate

**Description:** Upon adding/enrolling an authenticator with endpoint `POST https://{{idp_domain}}/mfa/associate`, it would be very useful to have the `id` of the authenticator being enrolled included in the response as well, in addition to the related `secret`.

**Use-case:** We are currently in preparation phase for the integration of Auth0’s Authentication API into our native app, with the goal of enabling native TOTP enrollments using the ROPC flow. This feature would enable us to maintain a local mapping of `authenticator_id` ↔ `totp_secret`, without abstracting that logic on our own. The native app will basically act as regular authenticator app. integrating native MFA with push notifications were not feasible for our use-case.  
In the end users will have the capability to enroll multiple devices, each TOTP enrollment bound to a single device. While the `authenticator_id` is not relevant for the MFA challenge, upon deletion of an MFA enrollment on one of those devices, the `id` will be relevant.  
While there would be a workaround to determine the `authenticator_id` by listing the user’s authenticators before and after the enrollment, this would come with the necessity of additional API calls, thus it might not be accurate in 100% of the cases.

---

<div class="post-metadata">

**Author:** ![dawid.matuszczyk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dawid.matuszczyk/32/74550_2.png) [@dawid.matuszczyk](https://community.auth0.com/u/dawid.matuszczyk)\
**Post date:** [May 29, 2025, 12:42pm UTC](https://community.auth0.com/t/mfa-including-authenticator-id-in-response-of-post-mfa-associate/186659/2 "2025-05-29T12:42:43Z")

</div>

Hi there!

Welcome to the Auth0 Community!

Thank you for creating this feedback card. Please make sure to upvote it so that it gets as many votes as possible and attracts as many community members as possible.

Thanks  
Dawid
