On Wed, 25 Jun 2014, Nathaniel McCallum wrote:
On Wed, 2014-06-25 at 13:21 +0300, Alexander Bokovoy wrote:
On Tue, 24 Jun 2014, Nathaniel McCallum wrote:
On Mon, 2014-06-02 at 23:07 -0400, Nathaniel McCallum wrote:
This HTTP call takes the following parameters:
* user
* password
*
On 06/26/2014 01:01 PM, Alexander Bokovoy wrote:
On Wed, 25 Jun 2014, Nathaniel McCallum wrote:
On Wed, 2014-06-25 at 13:21 +0300, Alexander Bokovoy wrote:
On Tue, 24 Jun 2014, Nathaniel McCallum wrote:
On Mon, 2014-06-02 at 23:07 -0400, Nathaniel McCallum wrote:
This HTTP call takes the
On Tue, 24 Jun 2014, Nathaniel McCallum wrote:
On Mon, 2014-06-02 at 23:07 -0400, Nathaniel McCallum wrote:
This HTTP call takes the following parameters:
* user
* password
* first_code
* second_code
* token (optional)
Using this information, the server will perform token synchronization.
On Wed, 2014-06-25 at 13:21 +0300, Alexander Bokovoy wrote:
On Tue, 24 Jun 2014, Nathaniel McCallum wrote:
On Mon, 2014-06-02 at 23:07 -0400, Nathaniel McCallum wrote:
This HTTP call takes the following parameters:
* user
* password
* first_code
* second_code
* token (optional)
On Mon, 2014-06-02 at 23:07 -0400, Nathaniel McCallum wrote:
This HTTP call takes the following parameters:
* user
* password
* first_code
* second_code
* token (optional)
Using this information, the server will perform token synchronization.
If the token is not specified, all
This HTTP call takes the following parameters:
* user
* password
* first_code
* second_code
* token (optional)
Using this information, the server will perform token synchronization.
If the token is not specified, all tokens will be searched for
synchronization.
Otherwise, only the token