Databases
StackOverflow2013
Postsdbo
POGoogle API -> Create a new Calendar -> Parse Error
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGoogle API -> Create a new Calendar -> Parse Error
    primarykey
    data
    text
    <p>I'm trying to create a Calendar through the Google API as per the <a href="https://developers.google.com/google-apps/calendar/v3/reference/calendars/insert" rel="nofollow">documentation</a>. I am trying to avoid using the Client libraries and do all communication with the API through custom webrequests and so far that has been working nicely but on this particular one I'm struggling with a <em>"parse error"</em>.</p> <p>Please do not refer to solutions that use the client libraries (<em>service.calendars().insert(...)</em>).</p> <p>This is a dumbed down version of my code (still not working):</p> <pre class="lang-cs prettyprint-override"><code>var url = string.Format ( "https://www.googleapis.com/calendar/v3/calendars?key={0}", application.Key ); var httpWebRequest = HttpWebRequest.Create(url) as HttpWebRequest; httpWebRequest.Headers["Authorization"] = string.Format("Bearer {0}", user.AccessToken.Token); httpWebRequest.Method = "POST"; httpWebRequest.ContentType = "application/json"; httpWebRequest.CookieContainer = new CookieContainer(); // Obviously the real code will serialize an object in our system. // I'm using a dummy request for now, // just to make sure that the problem is not the serialization. var requestText = "{" + Environment.NewLine + "\"summary\": \"test123\"" + Environment.NewLine + "}" + Environment.NewLine ; using (var stream = httpWebRequest.GetRequestStream()) using (var streamWriter = new System.IO.StreamWriter(stream)) { streamWriter.Write(System.Text.Encoding.UTF8.GetBytes(requestText)); } // GetSafeResponse() is just an extension that catches the WebException (if any) // and returns the WebException.Response instead of crashing the program. var httpWebResponse = httpWebRequest.GetSafeResponse(); </code></pre> <p>As you can see, I've given up on sending serialized objects for now and I'm just trying to get it working with a very simple dummy request:</p> <pre><code>{ "summary": "test123" } </code></pre> <p>Yet the response is still just:</p> <pre><code>{ "error": { "errors": [ { "domain": "global", "reason": "parseError", "message": "Parse Error" } ], "code": 400, "message": "Parse Error" } } </code></pre> <p>The accessToken is valid and not expired, the application key is correct.</p> <p>What am I doing wrong or missing?</p> <p>Thanks in advance,</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJan Van Herck
    1. USJan Van Herck
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COHi there just out of interest why are you adverse to using the client libraries?
      singulars
      1. POGoogle API -> Create a new Calendar -> Parse Error
      1. USDavid Waters
    2. COBecause it just adds another layer of complexity to an already quite complicated project, because we'd have to include code that is not under our control and that we perhaps can't fix ourselves when it bugs and/or breaks, and because REST services are, by definition, supposed to be simple and straightforward. Our code also synchronizes with FB and Twitter using the same no-nonsense approach, it is not difficult at all unless, like in this case, the documentation is wrong.
      singulars
      1. POGoogle API -> Create a new Calendar -> Parse Error
      1. USJan Van Herck
    3. COThanks for the response :)
      singulars
      1. POGoogle API -> Create a new Calendar -> Parse Error
      1. USDavid Waters
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload