Returns a new, randomly generated password for the current username. The new password is effective immediately. Passwords
do not expire, but Verizon recommends changing your password every 90 days.
There are three popular strategies for managing Wireless Network Services API log in credentials:
- One username for all API requests
- The simplest method for managing API log in credentials is to only have one username and password, and use those credentials
for all API requests. If you use multiple servers, it may be best to save the password in your database and use the
credentials from the database when calling the LogIn API.
- One username for each department or group
- If your organization has multiple departments or groups that work with M2M devices, you may want to have a separate username
and password for each group. For example, if one group is responsible for all new activations and another group is
responsible for changes to existing lines, having separate credentials allows you to know which group made each change
in the provisioning history of a device. It may be easier to track this information in your own application, though.
Note that access to APIs is not restricted by username, but you can write your application to restrict access to only
- One Wireless Network Services username; separate application user accounts
- For organizations that require the highest level of access control and accountability, the M2M provisioning application
that you develop should have its own set of user accounts, possibly tied in with corporate accounts. Your M2M application
can track which users make provisioning changes, and use a single Wireless Network Services username for all M2M Platform
API requests. Note that access to APIs is not restricted by username, but you can write your application to restrict
access for different users.
The M2M Platform locks a username after 5 consecutive failed log in attempts. You must contact M2M Support to get the username
||The current password for the account.
||The new active password for the account.
Example SOAP Request
Example SOAP Response
<Output xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns:a="http://schemas.datacontract.org/2004/07/NPhase.UnifiedWebService.APIs.v2.Contract.AccountService" >
Request Schema Diagram
Response Schema Diagram