Nick
unread,Sep 8, 2012, 6:01:32 PM9/8/12Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to google-ca...@googlegroups.com
I'm struggling to find adequate Google documentation to lead me in the right direction for what I'm trying to accomplish on a website for a client. I have years of experience using php, apis, and even facebook website applications. But for some reason, the Google documentation is cumbersome and I can't find the right route to take and there seems to be no sample projects to illustrate a full working application.
Synopsis of overall goal: A business's website will access one specific Google calendar used at the business to display appointment slot openings on given website. Each person at the business has access to the google calendar to add appointments via their google account. The website essentially needs to access this calendar server side to read the calendar events to determine appointment slot openings so website visitors can schedule an appointment.
I want to use the newest API obviously, Calendar API v3. I have my project in the API console. However I am very stumped on how you go about defining and using API access using PHP code server side on the website. Google want you to use OAuth 2.0, but this seems to force each website visitor to log in via their google account, so a website application can access that user's information. This is not what I want. It appears "maybe" the best route would be to use a "Service Account", but that is not enabled for the Google Calendar, and there doesn't seem to be any examples on how to use Service Account credentials anyways. Other client IDs can be for web application, and installed application (again I don't think these are correct due to user logging in and allowing access to their info). There is also the Simple API Access using a key for server apps using IP address locking, and a api key for web browser apps. How do all these relate to Google Calendar use the way I described? Google insists on using
OAuth 2.0, and older simple REST calls and v1 methods either don't work or will depreciated. Google does not provide information to guide a developer on what to do, how get this setup and working. What is proper authorization setup and use for a single Google calendar via server-side php code?
Any information on how to correctly go about this, or point to a API v3 sample would be great. This seems like this "should" be a simple matter, but for some reason it is incredibly complicated and not fully documented on Google's end on how to do this.