Good question. I can't think of any way that it would; the Dispatch oauth implementation doesn't look at the content type. If you want to be completely certain you can add that header that they reference to the token exchange requests, by copying the dispatch.twitter.Auth objects using <:<. I would do it myself but I'm leaving for a trip very soon. If there is a problem, I can certainly get a fix out before April 20th.