# Inserting Metadata Into Requests

**URL:** <https://community.auth0.com/t/inserting-metadata-into-requests/70491>\
**Category:** Get Help\
**Tags:** m2m, api\
**Created:** [September 29, 2021, 2:16pm UTC](https://community.auth0.com/t/inserting-metadata-into-requests/70491 "2021-09-29T14:16:31Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mmbmf1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mmbmf1/32/26154_2.png) [@mmbmf1](https://community.auth0.com/u/mmbmf1)\
**Post date:** [September 29, 2021, 8:39pm UTC](https://community.auth0.com/t/inserting-metadata-into-requests/70491/2 "2021-09-29T20:39:45Z")

</div>

Hi @a.pinzon,

Related to your post here: [Multiple users for Machine to Machine applications - #3 by a.pinzon](https://community.auth0.com/t/multiple-users-for-machine-to-machine-applications/70444/3) there might be a couple of ways to do this.

You can add properties to an id token for a user via Auth0 Actions: [Auth0 Actions](https://auth0.com/docs/actions). During the login flow, you can validate the properties on the id token.

Alternatively, if your customers are requesting an access token to then hit your API, you could add scopes (permissions) with required metadata to the token to verify the correct merchant: [Scopes](https://auth0.com/docs/configure/apis/scopes).

---

_[View the full topic](https://community.auth0.com/t/inserting-metadata-into-requests/70491)._
