I'm trying to use GoToMeeting's API and making a POST request to create a meeting. At the moment, I'm just trying to hardcode the body of the meeting and send headers but I'm receiving and I'm invalid JSON error and not sure why. Here's the code for that route:

app.post('/new-meeting', (req, res) => {

  const headers = {
    'Content-Type': 'application/json',
    Accept: 'application / json',
    Authorization: 'OAuth oauth_token=' + originalToken
  };

  console.log('-----------------------------------------------------------')
  console.log('Acess Token:');
  console.log('OAuth oauth_token=' + originalToken);
  console.log('-----------------------------------------------------------')

  const meetingBody = {
    subject: 'string',
    starttime: '2018-03-20T08:15:30-05:00',
    endtime: '2018-03-20T09:15:30-05:00',
    passwordrequired: true,
    conferencecallinfo: 'string',
    timezonekey: 'string',
    meetingtype: 'immediate'
  };

  return fetch('', {
    method: 'POST',
    body: meetingBody,
    headers: headers
  }).then(response => {

    console.log('response:');
    console.log(response);


    response
      .json()
      .then(json => {
        res.send(json);
        console.log(req.headers);
      })
      .catch(err => {
        console.log(err);
      });
  });
});

When I hit that router, I get the following error:

{
  "error": {
    "resource": "/rest/meetings",
    "message": "invalid json"
  }
}

Any advice would be appreciated!

I'm trying to use GoToMeeting's API and making a POST request to create a meeting. At the moment, I'm just trying to hardcode the body of the meeting and send headers but I'm receiving and I'm invalid JSON error and not sure why. Here's the code for that route:

app.post('/new-meeting', (req, res) => {

  const headers = {
    'Content-Type': 'application/json',
    Accept: 'application / json',
    Authorization: 'OAuth oauth_token=' + originalToken
  };

  console.log('-----------------------------------------------------------')
  console.log('Acess Token:');
  console.log('OAuth oauth_token=' + originalToken);
  console.log('-----------------------------------------------------------')

  const meetingBody = {
    subject: 'string',
    starttime: '2018-03-20T08:15:30-05:00',
    endtime: '2018-03-20T09:15:30-05:00',
    passwordrequired: true,
    conferencecallinfo: 'string',
    timezonekey: 'string',
    meetingtype: 'immediate'
  };

  return fetch('https://api.getgo./G2M/rest/meetings', {
    method: 'POST',
    body: meetingBody,
    headers: headers
  }).then(response => {

    console.log('response:');
    console.log(response);


    response
      .json()
      .then(json => {
        res.send(json);
        console.log(req.headers);
      })
      .catch(err => {
        console.log(err);
      });
  });
});

When I hit that router, I get the following error:

{
  "error": {
    "resource": "/rest/meetings",
    "message": "invalid json"
  }
}

Any advice would be appreciated!

• javascript
• json
• express

• Try JSON.stringify() your meetingBody object before putting into the body option, I do not think fetch automatically parses objects to json – Patrick Evans Commented Mar 21, 2018 at 16:34
• @PatrickEvans stringifying the body means the header needs to be changed, plus the api most likely accepts json in the body – mast3rd3mon Commented Mar 21, 2018 at 16:35
• @mast3rd3mon, no it doesn't. The header just tells the server what to expect, and since JSON is text and stringifying an object results in text the header does not need changed – Patrick Evans Commented Mar 21, 2018 at 16:36
• stringifying json turns it into text so the header bees text/plain – mast3rd3mon Commented Mar 21, 2018 at 16:37
• @mast3rd3mon — No, it doesn't. JSON.stringify outputs a JSON text. JSON text is not plain text. – Quentin Commented Mar 21, 2018 at 16:37

2 Answers 2

tl;dr

You are passing fetch a value for the body represented by a JavaScript object. It is converting it to a string by (implicitly) calling its .toString() method. This doesn't give you JSON. The API you are calling then plains and tells you that it isn't JSON.

You need to convert your object to JSON using:

body: JSON.stringify(meetingBody), 

Test case

This demonstrates the problem and the solution.

Server

This is designed to be a very primitive and inplete mock of GoToMeeting's API. It just echos back the request body.

const express = require("express");
var app = express();
var bodyParser = require('body-parser');

app.use(bodyParser.text({ type: "*/*" }));

app.post("/", (req, res) => {
    console.log(req.body);
    res.send(req.body)
});

app.listen(7070, () => console.log('Example app listening on port 7070!'))

Client

This represents your code, but with the Express server stripped out. Only the code relevant for sending the request to GoToMeeting's API is preserved.

const url = "http://localhost:7070/";
const fetch = require("node-fetch");

const headers = {
    'Content-Type': 'application/json',
    Accept: 'application / json',
    Authorization: 'OAuth oauth_token=foobarbaz'
};

const meetingBody = {
    subject: 'string',
    starttime: '2018-03-20T08:15:30-05:00',
    endtime: '2018-03-20T09:15:30-05:00',
    passwordrequired: true,
    conferencecallinfo: 'string',
    timezonekey: 'string',
    meetingtype: 'immediate'
};


fetch(url, {
        method: 'POST',
        body: meetingBody,
        headers: headers
    })
    .then(res => res.text())
    .then(body => console.log(body));

Results of running the test case

The logs of both server and client show:

[object Object] 

This is what you get when you call meetingBody.toString().

If you change the code as described at the top of this answer, you get:

{"subject":"string","starttime":"2018-03-20T08:15:30-05:00","endtime":"2018-03-20T09:15:30-05:00","passwordrequired":true,"conferencecallinfo":"string","timezonekey":"string","meetingtype":"immediate"}

This is JSON, which is what the API is expecting.

Aside

MIME types do not have spaces in them. Accept: 'application / json', should be Accept: 'application/json',. This probably isn't causing you any problems though.

I believe the header is incorrect.

You need 'Accept: application/json' without space.