@Gaston_Avila, a client token (aka application access token) can only be used to call resources that belong to the application itself which includes Webhooks, Webhook Subscriptions, and Events. The only exception to this is if you’re integrating with our white labeled Access API. If you’re an Access API partner then an application access token can be used to call resources that belong to the app as well as the
Account that “owns” the application.
The reason you’re seeing the Account link get returned in the Sandbox is that by default all applications in the Sandbox are enabled with a private scope called
ManageCustomers which determines if you can call resource that belong to the app as well as the account that the app belongs to.
If you’re integrating with our Access API then this is the correct method to obtain authorization for your app and account.
If you’re integrating with our Transfer solution and want to call the API on your own account’s behalf then you’ll need to implement the 3-legged OAuth flow and obtain an access token for your own user account. The alternative to going through the OAuth flow with your own account would be to generate a token for your own account as described in this article.