From 714c693147e1b7fa2b7916fbe2628dd70c7acfac Mon Sep 17 00:00:00 2001
From: hatuan195 <47517542+hatuan195@users.noreply.github.com>
Date: Mon, 27 Nov 2023 11:13:41 +0700
Subject: [PATCH] Update configuration.rst

The route for creating token has changed

Signed-off-by: hatuan195 <47517542+hatuan195@users.noreply.github.com>
---
 admin_manual/office/configuration.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/admin_manual/office/configuration.rst b/admin_manual/office/configuration.rst
index db215483175..841af5a8628 100644
--- a/admin_manual/office/configuration.rst
+++ b/admin_manual/office/configuration.rst
@@ -27,7 +27,7 @@ Enable access for external apps
 Nextcloud internally passes an access token to Collabora Online that is used later by it to do various operations. By default, it's not possible to generate this token by 3rd parties; only Nextcloud can generate and pass it to Collabora Online.
 
 In some applications, it might be necessary to generate the token by a 3rd party application. For this, one needs to add the 3rd party application (external apps) in this setting. You need to add an application identifier and a secret
-token. These credentials then can be used by the 3rd party application to make calls to `wopi/extapp/data/{fileId}` to fetch the access token and URL source for given fileId, both required to open a connection to Collabora Online.
+token. These credentials then can be used by the 3rd party application to make calls to `ajax/extapp/data/{fileId}` to fetch the access token and URL source for given fileId, both required to open a connection to Collabora Online.
 
 Canonical webroot
 *****************