The Disconnect (me/app) endpoint enables apps to properly disconnect from Nike+. Disconnect removes internal connections Nike+ makes to the app, expires the user’s access token, and verifies that the disconnection was successful.
It is important that apps call the Disconnect (/me/app) endpoint when users choose to disconnect the app from their Nike+ account. Logging out of Nike+ is not sufficient, since invoking a logout for the user does not clean up all of the user’s information on the Nike+ side.
Note: Calling the Disconnect (/me/app) endpoint is also important if the app uses Webhooks for notifications. Nike+ will continue to send notifications of new data to the registered callback URL if a subscribed app has not disconnected by calling the Disconnect (/me/app) endpoint.
When users choose to disconnect, they expect the app to no longer be connected to their Nike+ account. In order for this to occur, the app must disconnect by calling the Disconnect (/me/app) endpoint. Failing to properly disconnect an app from a user’s Nike+ account might adversely affect the user’s experience.
Note: If a user disconnects an app through the Nike+ website, Nike+ does not send a notification to the app.
Note: The test console is not available for the Disconnect (/me/app) endpoint.
|access_token||String||Yes||User's access token|