This is what the /apps/{accessTokens}/de-authenticate route does.

Passing valid access_tokens to this method causes the application that created them to be de-authorized by the user associated with each access_token. This will remove the application from their apps tab, and cause all other existing access_tokens (that they have on that app) to be destroyed.

So if you do not remember a valid access_token, create a temporary new one for that user and your app.

Then call /2.2/apps/{A_VALID_TOKEN_FOR_USER}/de-authenticate.

This will invalidate all of that user's tokens for your app.

This is what the /apps/{accessTokens}/de-authenticate route does.

Passing valid access_tokens to this method causes the application that created them to be de-authorized by the user associated with each access_token. This will remove the application from their apps tab, and cause all other existing access_tokens to be destroyed.

^{(Emphasis added)}

So if you do not remember a valid access_token, create a temporary new one for that user and your app.

Then call /2.2/apps/{A_VALID_TOKEN_FOR_USER}/de-authenticate.

This will invalidate all of that user's tokens for your app.