Re: Why blogger api need a manual request approval?
Nashwan Alsarafi <[email protected]>
| Newsgroups | gmane.comp.web.blogger.api |
|---|---|
| Message-ID | <[email protected]> |
I lodged an application five days aago to get the API 3 key and was told that the application proocess should only take five days for reviewing its been more than five days now and still no reply from the blogger's team, Can you help me thanks On Monday, September 17, 2012 12:48:19 PM UTC-7, Brett Morgan wrote: > > Hi Ribhararnus, > > The decision to make Blogger API v3 access require manual approval is > because of the maturity level of the API. If you look on the APIs Console, > you will see a number of Google’s APIs are in Limited Availability. > > The advantage for developers here is that throughout the sign up process > we have a direct line of contact with each other, should a developer’s apps > cause problems in our backends. It also means that developers have an email > from me in their inbox encouraging them to contact me if they hit a > roadblock in using our APIs. > > As our confidence in the Blogger API grows, we will push it to General > Availability, and at that point the API will no longer require the current > manual request cycle with me for initial usage quota. However, requesting > additional quota over and above the initial quota will still require a > conversation with our team, detailing what the application is doing. This > conversation is mainly to make sure that the quota is being used > effectively and efficiently, and to make sure our Terms of Service are > being adhered to. > > I hope this clarifies the reasoning behind the current requirement to > request access to Blogger API v3. > > brett > > > On Fri, Sep 14, 2012 at 3:57 PM, Ribhararnus Pracutiar < > [email protected] <javascript:>> wrote: > >> I want to know, what a reason blogger team decided that blogger api v3 >> should be throught a manual request approval? >> >> And, Is blogger xmlrpc has no longer available? Why people/Developer has >> no right tofree access? It seems for me such a limitting freedom of speech.. >> >> ps: Sorry for myenglish grammar, I'm not native speaker, and I just pure >> curious about this topic. Thanks >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Blogger Developer Group" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/bloggerdev/-/dT8_m63UFhkJ. >> To post to this group, send email to [email protected] >> <javascript:>. >> To unsubscribe from this group, send email to >> [email protected] <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/bloggerdev?hl=en. >> >> > > > -- > > Brett Morgan | Developer Relations Engineer, Google+ | [email protected] > <javascript:> | profiles.google.com/brettmorgan > -- You received this message because you are subscribed to the Google Groups "Blogger Developer Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/bloggerdev. For more options, visit https://groups.google.com/d/optout.