# Custom Domain Custom Push Notification - put-pn-providers

**URL:** <https://community.auth0.com/t/custom-domain-custom-push-notification-put-pn-providers/189465>\
**Category:** Get Help\
**Tags:** push-via-auth0-guardian-factor, mfa\
**Created:** [July 21, 2025, 2:11pm UTC](https://community.auth0.com/t/custom-domain-custom-push-notification-put-pn-providers/189465 "2025-07-21T14:11:51Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jrceja313](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jrceja313/32/72177_2.png) [@jrceja313](https://community.auth0.com/u/jrceja313)\
**Post date:** [July 21, 2025, 2:11pm UTC](https://community.auth0.com/t/custom-domain-custom-push-notification-put-pn-providers/189465/1 "2025-07-21T14:11:51Z")

</div>

I am attempting to setup the push notification from my mobile app using the Auth0 SDK.

Our copy link for the push notification enrollment appears to use the non custom domain url.

I found [https://auth0.com/docs/api/management/v2/guardian/put-pn-providers](https://auth0.com/docs/api/management/v2/guardian/put-pn-providers) but am having an issue putting the custom provider pn in place.

It is returning a 400 and I am not finding any documentation around this.

Thank you!

---

<div class="post-metadata">

**Author:** ![vlad.murarasu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/vlad.murarasu/32/72793_2.png) [@vlad.murarasu](https://community.auth0.com/u/vlad.murarasu)\
**Post date:** [July 21, 2025, 3:19pm UTC](https://community.auth0.com/t/custom-domain-custom-push-notification-put-pn-providers/189465/3 "2025-07-21T15:19:28Z")

</div>

Hi @jrceja313,

The endpoint provides an error message to explain what the error is.

Example:

Body:

```auto
{
  "provider": "vgyub"
}

```

Response:

```auto
{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Payload validation error: 'Invalid value \"vgyub\"' on property provider.",
  "errorCode": "invalid_body"
}

```

The endpoint’s documentation says that the 400 error occurs due to `Invalid input based on schemas`. Could you provide the body of your request?

Have a good one,  
Vlad

---

<div class="post-metadata">

**Author:** ![jrceja313](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jrceja313/32/72177_2.png) [@jrceja313](https://community.auth0.com/u/jrceja313)\
**Post date:** [July 21, 2025, 3:31pm UTC](https://community.auth0.com/t/custom-domain-custom-push-notification-put-pn-providers/189465/4 "2025-07-21T15:31:28Z")

</div>

Body:  
{  
“provider”: “custom”  
}

Response:  
{  
“statusCode”: 400,  
“error”: “Bad Request”,  
“message”: “Payload validation error: ‘Invalid value "custom"’ on property provider.”,  
“errorCode”: “invalid\_body”  
}

---

<div class="post-metadata">

**Author:** ![vlad.murarasu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/vlad.murarasu/32/72793_2.png) [@vlad.murarasu](https://community.auth0.com/u/vlad.murarasu)\
**Post date:** [July 21, 2025, 3:38pm UTC](https://community.auth0.com/t/custom-domain-custom-push-notification-put-pn-providers/189465/5 "2025-07-21T15:38:32Z")

</div>

Hi @jrceja313,

Whenever you receive an `invalid_body` error for an endpoint, expand the `BODY PARAMETERS` section to see what rules must be applied.

 ![Screenshot 2025-07-21 at 6.33.32 PM](https://global.discourse-cdn.com/auth0/original/3X/6/5/6587b7364d9d2b5b632dfb2b2491e9c1a7b6fd1a.png)

In this case, the `Update Push Notification configuration` endpoint can only receive `guardian`, `sns`, or `direct` as input.

If you have any other questions, feel free to reach out.

Have a good one,  
Vlad

---

<div class="post-metadata">

**Author:** ![jrceja313](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jrceja313/32/72177_2.png) [@jrceja313](https://community.auth0.com/u/jrceja313)\
**Post date:** [July 21, 2025, 3:48pm UTC](https://community.auth0.com/t/custom-domain-custom-push-notification-put-pn-providers/189465/6 "2025-07-21T15:48:52Z")

</div>

Okay, that may be a misinterpretation on my part.  
How do I get my Copy Code for push notification to have the base\_url to point at my custom domain.

Thank you,  
Jeff

---

<div class="post-metadata">

**Author:** ![jrceja313](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jrceja313/32/72177_2.png) [@jrceja313](https://community.auth0.com/u/jrceja313)\
**Post date:** [July 21, 2025, 3:56pm UTC](https://community.auth0.com/t/custom-domain-custom-push-notification-put-pn-providers/189465/7 "2025-07-21T15:56:25Z")

</div>

I have created a support ticket for this as it may be similar to early access features and is not configurable in the tenant.

---

<div class="post-metadata">

**Author:** ![vlad.murarasu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/vlad.murarasu/32/72793_2.png) [@vlad.murarasu](https://community.auth0.com/u/vlad.murarasu)\
**Post date:** [July 21, 2025, 4:46pm UTC](https://community.auth0.com/t/custom-domain-custom-push-notification-put-pn-providers/189465/8 "2025-07-21T16:46:54Z")

</div>

Hi @jrceja313,

You can find everything about setting up push notifications, including setting up the Google Play and Apple Store URLs, in this article:

> **[Configure Push Notifications for MFA](https://auth0.com/docs/secure/multi-factor-authentication/multi-factor-authentication-factors/configure-push-notifications-for-mfa)**
>
> Describes how to configure push notifications for MFA.

The easiest way to configure it would be through the Auth0 Dashboard, at `Security > Multi-factor Auth > Push Notification using Auth0 Guardian`.

If you have any other questions, feel free to reach out.

Have a good one,  
Vlad

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [August 4, 2025, 4:47pm UTC](https://community.auth0.com/t/custom-domain-custom-push-notification-put-pn-providers/189465/9 "2025-08-04T16:47:06Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
