# Form Vault Connection Bad request

**URL:** <https://community.auth0.com/t/form-vault-connection-bad-request/200386>\
**Category:** Get Help\
**Tags:** users, management-api\
**Created:** [May 29, 2026, 11:54am UTC](https://community.auth0.com/t/form-vault-connection-bad-request/200386 "2026-05-29T11:54:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![gerald.czifra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gerald.czifra/32/75301_2.png) [@gerald.czifra](https://community.auth0.com/u/gerald.czifra)\
**Post date:** [May 29, 2026, 10:47pm UTC](https://community.auth0.com/t/form-vault-connection-bad-request/200386/3 "2026-05-29T22:47:18Z")

</div>

Hi @k.guy

Welcome to the Auth0 Community!

I understand that you are receiving a " Payload validation error: 'Data does not match any schemas " error message when attempting to create a Form Vault Connection. There could be different reasons for this issue, please allow me to detail:

- you could be using `https://` or [Slashes in the domain](https://auth0.com/blog/whats-new-in-the-auth0-terraform-provider/). Please ensure it is under the correct format of “domain”: “[your-tenant.us.auth0.com](http://your-tenant.us.auth0.com)” without `https://`;

- your tenant domain name starts with a numeric digit. We have had [a report](https://community.auth0.com/t/issue-with-auth0-vault-creation/182523/11) of this issue that had this cause and the solution to removing the error was to remove the starting numerical digit from the domain name;

- ensure that your M2M application has the [correct scopes](https://community.auth0.com/t/cannot-create-a-flow-vault-connection-as-the-permission-is-not-in-my-token/187889/2) in the access token. It will require to have the `create:flows_vault_connections` and `update:flows_vault_connections` scopes granted and authorized.

Let us know if this helped you clear the issue!

Best regards,  
Gerald

---

_[View the full topic](https://community.auth0.com/t/form-vault-connection-bad-request/200386)._
