Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:sidebar:remoteapi:apiref:core:reset_password_request [25/01/2013 13:43]
zuve
en:sidebar:remoteapi:apiref:core:reset_password_request [31/07/2020 07:16] (current)
chdi [Password reset request]
Line 2: Line 2:
 ====== Password reset request ====== ====== Password reset request ======
  
-To send a password reset request use command **core/​reset_password_request**: ​+To send a password reset requestuse the command **core/​reset_password_request**: ​
 <code javascript>​ <code javascript>​
 svc=core/​reset_password_request&​params={"​user":<​text>,​ svc=core/​reset_password_request&​params={"​user":<​text>,​
  "​url":<​text>,​  "​url":<​text>,​
- "​email":<​text>,​ + "​email":<​text>​}
- "​emailFrom":<​text>​}+
 </​code>​ </​code>​
  
 +Request execution is 1 time per 1 minute, in other case returns "​error":​11 - reason: "​REQUEST_TOO_OFTEN"​
 ===== Parameters ===== ===== Parameters =====
 ^ Name ^ Description ^ ^ Name ^ Description ^
 | user | user name | | user | user name |
-| url | URL contained in the letter that will be sent to user at password reset request: <​url>?​user=<​login>&​passcode=<​passcode>​ (value of passcode see in [[reset_password_perform]])|+| url | URL contained in the letter that will be sent to the user at password reset request: <​url>?​user=<​login>&​passcode=<​passcode>​ (the value of //passcode// see in [[reset_password_perform|]])|
 | email | user e-mail | | email | user e-mail |
-| emailFrom | e-mail from which confirmation e-mail will be sent | 
  
 ===== Response ===== ===== Response =====
Line 23: Line 22:
 } }
 </​code>​ </​code>​
-Also another ​types of errors ​can be returnedThe whole list of them you can find in chapter [[../​errors/​errors]]+Other types of errors ​may occurSee the full list in the chapter [[../​errors/​errors]].
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2024 Gurtam