# Override Notification URL

This is a feature that intended to override the configured `Notification URL` from API request level. When the override URL is defined on request level, then the notification will be send to the newly destined URL instead of the configured one.  To override, make sure you already configure the `Notification URL` on DOKU Back Office.

{% hint style="info" %}
**Override URL path must be the same as the configured `Notification URL` path**

For example, if the configured URL is `https://example.com/payments/notifications` , then the override URL must be `https://anotherexample.com/payments/notifications` .  As you can see that both URL contains `payments/notifications` which is the same path.
{% endhint %}

{% hint style="warning" %}
**You can't use the same domain with different path**

You can change the domain or sub-domain, but it is mandatory to make sure the override URL and the configured `Notification URL` have the same path, otherwise this features won't work.
{% endhint %}

### How To Use

When requesting payment, you have to add this parameter under the additional info on the request body.

```json
{
...
    "additional_info": {
        "override_notification_url": "https://anotherexample.com/payments/notifications"
    }
...
}
```

The `override_notification_url` parameter is used for overriding URL, you can simply fill the value with your override URL. After this, all payment notification in this specific channel will be sent to the new destined URL. 


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developers.doku.com/get-started-with-doku-api/notification/override-notification-url.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.