Skip to main content
Every connected profile carries a status. Two different things are being reported, and they are independent of each other: whether the authorization still works, and whether billing entitles you to use the profile.

What you see in the dashboard

Paused — billing outranks the other two in the table. If billing has lapsed, saying Active would be technically true and useless — the profile is not being served either way.

What your code sees

The API reports these as two separate fields, because they need different handling: Suspended profiles are still returned by the profiles endpoint rather than hidden. A profile that silently vanished from a list would read to your users as a deleted account, which is not what happened.

Reconnect

An authorization stops working when someone changes the account password, removes Nylon from the network’s connected-apps list, changes who administers a Facebook Page, or simply lets the network’s own token expiry lapse. Nylon refreshes tokens continuously, but it cannot refresh one that has been revoked.

An account says Reconnect

How to clear it, and how to be told about it before your users are.

Paused — billing

Your first two connected accounts are free. Beyond that, a live subscription is required, and if there is not one, the accounts past the free allowance are paused. The free slots go to your longest-connected profiles, so which two stay active is predictable rather than arbitrary. Nothing is disconnected and no credentials are destroyed. Restarting billing lifts every pause immediately, with no re-authorization.

Accounts paused for billing

Why it happens, and how to restore the paused accounts.

Being told about changes

You do not have to poll the profiles endpoint. Subscribe to profile.needs_attention, profile.connected and profile.disconnected and Nylon will call your server when a status changes.

Webhook events

The six events, and what each one carries.