Testing out Callback URL whitelisting ahead of launch

oauth
signin
callback

#1

In early May, we announced a new requirement for all developers using Sign in with Twitter to add whitelisted callback URLs to their application settings. We shared that these changes will be implemented on June 12th — at which point any callback URL not added to the whitelist will fail.

In preparation for next week’s implementation of these changes, today we are temporarily activating enforcement of whitelisted callback URLs for a random sample of some API requests to oauth/request_token. Our intention with today’s campaign is to alert developers who may not have seen our May announcement and to encourage whitelisting as soon as possible.

Developers who have not yet whitelisted their callback URLs can do so by following the guidance in the May forum post. Additionally, you may visit the documentation for more detail. It is important that you make this change before Tuesday, June 12th to avoid any interruption.

Developers who have already whitelisted their URLs will not be impacted by today’s campaign and will not experience interruption next week.


#2

#3