Inactive Account or Client

It rarely happens, but sometimes we find something in a developer account or product that violates our policies, and we are forced to inactivate it until we can get more information.

Account inactive

We may need to inactivate your developer account if we find that you have not complied with:

You will see the following banner on your profile page:

Account inactive

How this affects you and your customers

When a developer account is inactive:

What to do if you get this notice in your profile page

When your account is inactive, your customers are not affected, but you cannot create new Works with Nest clients.

Use the account email address that you sign into console.developers.nest.com with.

Client inactive

We may need to inactivate a client if we find that you have not complied with:

  • Nest design policies
  • Works with Nest store policy
  • Nest Developer prohibitions (you agreed to these prohibitions when you created your account) - check your profile to review

You will see the following banner on your OAuth Clients page:

Client inactive

How this affects you and your customers

When a client is inactive:

  • Customers are affected - their Works with Nest connections will fail because access tokens no longer function
  • You cannot create new authorization codes or access tokens
  • Open connections will continue to work, but if the connection is lost/closed, you cannot reconnect

What to do if you get this notice in your client page

When your client is inactive, your customers cannot use your Works with Nest product.

Use the account email address that you sign into console.developers.nest.com with. Your Client ID is found on the Overview tab of the OAuth Client.

Troubleshooting

If you get a 403 Forbidden error when you access the API, check your Clients page for more information. Your account or client may have been tagged inactive, and you should contact us to resolve the issue.