diff options
| author | Sebastian <sebasjm@gmail.com> | 2023-09-08 11:10:43 -0300 |
|---|---|---|
| committer | Sebastian <sebasjm@gmail.com> | 2023-09-14 11:57:55 -0300 |
| commit | e9268f18c02a634d4dd564cff33ea6fccd676a03 (patch) | |
| tree | af7d8be090f43a717ec7b9ce2edc07eec1d3193c /core/api-merchant.rst | |
| parent | 2c37f7764a657b6d06e364ca6f22eb72163ab1f3 (diff) | |
| download | docs-e9268f18c02a634d4dd564cff33ea6fccd676a03.tar.gz docs-e9268f18c02a634d4dd564cff33ea6fccd676a03.tar.bz2 docs-e9268f18c02a634d4dd564cff33ea6fccd676a03.zip | |
token instead of login
Diffstat (limited to 'core/api-merchant.rst')
| -rw-r--r-- | core/api-merchant.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/core/api-merchant.rst b/core/api-merchant.rst index 732a35b1..3239db23 100644 --- 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. |