RE: Re: Obtaining a blogger api key

"Brian Dance" <[email protected]>
Newsgroups gmane.comp.web.blogger.api
Organization Ironstone Software
Message-ID <[email protected]>
I think the last message in this email went to the wrong address.
From: [email protected] [mailto:[email protected]] On
Behalf Of Samantha Chan
Sent: Thursday, 21 November 2013 6:10 PM
To: [email protected]
Subject: Re: [bloggerDev] Re: Obtaining a blogger api key
 
Hi Brett,
 
I was unable to active the Blogger API from your email. I get the "You don't
have permission for that operation" error message, can you help me what I
need to do to work around this issue?
 
thanks,
Sam

On Tuesday, November 12, 2013 5:28:16 PM UTC-8, Brian Dance wrote:
Thanks.
 
From: [email protected] <javascript:>
[mailto:[email protected] <javascript:> ] On Behalf Of Brett Morgan
Sent: Wednesday, 13 November 2013 11:35 AM
To: [email protected] <javascript:> 
Subject: Re: [bloggerDev] Re: Obtaining a blogger api key
 
 
 
On Wed, Nov 13, 2013 at 10:34 AM, Brian Dance
<[email protected] <javascript:> > wrote:
Hi Brett,
 
I just realised that if I select Blogger V3 API I get the page with the
status OFF and if you click that you get the request page.
I have resent the request. 
 
I'll generate a new batch of invites shortly
 
As mentioned, I will be wanting to use this for several clients, so will I
need to create a fresh request for each, or can I use my ironstone account
for all. 
 
By default, a Key has a quota of 10k requests per day. It would be sane to
have each of your clients request their own key, thus if they need more than
10k requests then I can evaluate their website / webapp and privacy
statement as a standalone entity, not as part of a group of unrelated sites
with different privacy statements et al.
 
Note that I hope to use blogger on my community sites (soccer club, school,
etc.) where the users can easily update blogs that will appear on the
website. This makes it easier for everybody to get the details out.
 
I understand your use case, but you will either need to add each user to
your blog as an editor (for default OAuth flow), or set up some system where
you can have them post as you on the blog, which has a bunch of
impersonation issues. I strongly advocate going with the system of adding
everyone who might post as an author on the blog, thus you will be able to
properly attribute content, and revoke authorship if required, while not
having to maintain your own authentication scheme.
 
 
Cheers,
Brian
 
From: [email protected] <javascript:>
[mailto:[email protected] <javascript:> ] On Behalf Of Brett Morgan
Sent: Wednesday, 13 November 2013 9:41 AM
To: [email protected] <javascript:> 
Subject: Re: [bloggerDev] Re: Obtaining a blogger api key
 
Hi Brian, Can you please re-apply? My records show that I sent you an email,
but I can't find it in my outbox. Weird.
 
(It's not an automated process, fwiw)
 
On Wed, Nov 13, 2013 at 9:36 AM, <[email protected]
<javascript:> > wrote:
I requested an API KEY about a week ago and still haven't heard anything.
I'm hoping to use the Blogger JSON API on many of my clients websites, but
I'm concerned about the response time if it takes a week or more for each
request.
Is there any reason it takes so long and will I get an API key for each
request?
 
Brett can you please clarify the process and why it takes so long for what
could be an automated response.


On Sunday, 27 October 2013 02:31:44 UTC+11, Booklrs Tumblebooks wrote:
Instead of opening a new topic I join this one. Brett, can you let us know
when the next batch of invites are send? Thanks!


Op zondag 19 augustus 2012 22:35:46 UTC+2 schreef Alex Alden:
I've been trying to obtain a blogger api key by filling out the "Blogger
JSON API Quota Request" form. But I was getting no response, no email and no
key :( Am I doing something wrong? Can somebody please explain me the
process. Thanks.
-- 
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] <javascript:> .
To post to this group, send email to [email protected] <javascript:>
.
Visit this group at http://groups.google.com/group/bloggerdev.
For more options, visit https://groups.google.com/groups/opt_out.



 
-- 
 
Brett Morgan | Developer Relations Engineer, Google Maps |
[email protected] <javascript:>  | profiles.google.com/brettmorgan
-- 
You received this message because you are subscribed to a topic in the
Google Groups "Blogger Developer Group" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/bloggerdev/CkC7JtxNWig/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected] <javascript:> .

To post to this group, send email to [email protected] <javascript:>
.
Visit this group at http://groups.google.com/group/bloggerdev.
For more options, visit https://groups.google.com/groups/opt_out.
-- 
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] <javascript:> .
To post to this group, send email to [email protected] <javascript:>
.
Visit this group at http://groups.google.com/group/bloggerdev.
For more options, visit https://groups.google.com/groups/opt_out.



 
-- 
 
Brett Morgan | Developer Relations Engineer, Google Maps |
[email protected] <javascript:>  | profiles.google.com/brettmorgan
-- 
You received this message because you are subscribed to a topic in the
Google Groups "Blogger Developer Group" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/bloggerdev/CkC7JtxNWig/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected] <javascript:> .
To post to this group, send email to [email protected] <javascript:>
.
Visit this group at http://groups.google.com/group/bloggerdev.
For more options, visit https://groups.google.com/groups/opt_out.
-- 
You received this message because you are subscribed to a topic in the
Google Groups "Blogger Developer Group" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/bloggerdev/CkC7JtxNWig/unsubscribe.
To unsubscribe from this group and all its topics, 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/groups/opt_out.

-- 
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/groups/opt_out.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.