Twitter API Approval Issue

[jkmdev]

TL;DR: Are attachments completely ignored in all steps of the twitter application process?

My group and I have been attempting to get approval to use the API for a school project of ours. We’ve been twice prompted to send more information about our application, each time told to provide more.

In our latest attempt, we sent an email with an attached two page document outlining our project, core use case, and how we’d plan on using the API to obtain data for it. Less than 10 minutes after it was sent, we got a reply telling us to send even more information, and that we’d be rejected if it weren’t sufficient this time around.

My concern is that, maybe, we got this response because the information was attached instead of included in the body of the email itself. Considering how quickly it was (partially) rejected, it seemed a bit weird to me. Is that the case?

[Aurelia]

Hi - there are two options here: (1) either your attachement somehow went unnoticed, or (2) the information provided in your attachement still didn’t contain the right information.

My advice is to respond to this second email asking for more information by providing an answer for each bullet point in as much detail as possible. If a question doesn’t seem relevant to your use case, make sure to say so and explain why it isn’t relevant. Make sure to provide this information as part of the body of your email, rather than in an attachement, to avoid information getting lost.

Let us know if you need any more help.

[jkmdev]

Thanks for the help! And alright, we’ll have to keep those things in mind for our next response. If we have any extra questions I’ll probably make a new thread for it.

[LeBraat]