Skip to main content
Disconnecting removes a social profile from your organization and destroys the credential Nylon stored for it. This is not a soft toggle — there is no stored token left behind to reattach to.

​
Disconnect a profile

Open Connections, find the row, open the ⋯ menu at the end of it, and select Disconnect.

​
What happens

Nylon clears the encrypted credential on the profile as part of the same transaction that marks it disconnected. Nothing is kept for later.
API calls that target it fail from that moment. It no longer appears in your connected profiles.
Connected accounts are what you are billed for, so disconnecting one is reflected in your subscription. See How pricing works.
Subscribers are told, so your own database can be kept in step without polling.

​
Also revoke Nylon at the network

Disconnecting destroys Nylon’s copy of the credential, which is the part Nylon controls. It does not, and cannot, tell the network to forget that it once issued one. If you are disconnecting because a client relationship ended, or because you are handing an account back, finish the job on the network itself — remove Nylon from the connected-apps or business-integrations list in that account’s own settings. That is what guarantees no further access, and it is worth doing regardless of what Nylon stores.

​
Reconnecting later

You can connect the same account again at any time. It goes through the full authorization flow, because there is no credential left to reuse.
If the authorization has merely stopped working, reconnect instead of disconnecting. Reconnecting keeps the profile id your application already stored; disconnecting and connecting again may not.

What Nylon stores

Credentials, request bodies and webhook payloads.

How pricing works

You are billed per connected account.