commit e9268f18c02a634d4dd564cff33ea6fccd676a03
parent 2c37f7764a657b6d06e364ca6f22eb72163ab1f3
Author: Sebastian <sebasjm@gmail.com>
Date: Fri, 8 Sep 2023 11:10:43 -0300
token instead of login
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -107,7 +107,7 @@ Currently, the API supports two main authentication methods:
header, where ``$TOKEN`` is a secret authentication token configured for the instance which must begin with the RFC 8959 prefix.
Additionally, clients can send a **login token** which they may obtain from
-the ``/private/login`` endpoint. Such a login token is valid only for a
+the ``/private/token`` endpoint. Such a login token is valid only for a
limited period of time and can be used by clients to avoid storing the
long-term login secrets from an authentication method.
