Use a REST API: Difference between revisions

Line 24:

Note that this version doesn't include code to submit events to Meetup.

<~~lang~~ go>package main

<syntaxhighlight lang="go">package main

import (

Line 147:

fmt.Println("First event:\n", &evresp.Results[0])

}

}</~~lang~~>

}</syntaxhighlight>

<pre>

Line 163:

Note that this code is untested as you need a paid subscription to create events which I don't have.

<~~lang~~ go>package main

<syntaxhighlight lang="go">package main

import (

Line 260:

check(err)

fmt.Printf("The %q event has been cancelled.\n", event.Name)

}</~~lang~~>

}</syntaxhighlight>

=={{header|Java}}==

Line 268:

EventGetter.java

<~~lang~~ java>package src;

<syntaxhighlight lang="java">package src;

import java.io.BufferedReader;

Line 326:

}

}</~~lang~~>

}</syntaxhighlight>

Main.java

<~~lang~~ java>/*

<syntaxhighlight lang="java">/*

* In this class, You can see the diferent

* ways of asking for events.

Line 418:

}

}</~~lang~~>

}</syntaxhighlight>

=={{header|JavaScript}}==

Line 424:

Made on node js. Run using 'node filename.js'

<~~lang~~ javascript>var fs = require('fs');

<syntaxhighlight lang="javascript">var fs = require('fs');

var request = require('request');

Line 567:

}, function(result) {

console.log('Event: ', result);

})</~~lang~~>

})</syntaxhighlight>

=={{header|Phix}}==

Line 573:

Unfortunately the API (V2) does not support creating events, so instead this shows how to use

a post method to toggle sales (but see note below).

--

-- demo\rosetta\Using_a_REST_API.exw

Line 681:

res = toggle_sales({"eventid",id,"status",status},"events/togglesales")

puts(1,print_json("",res))

Note that toggling sales off makes the (manually created) event invisible to the API, even without

the {"status","live"} filter, hence I had to hard-code the event id to permit a second run to turn

Line 746:

eventGetter.py

<~~lang~~ python>#http://docs.python-requests.org/en/latest/

<syntaxhighlight lang="python">#http://docs.python-requests.org/en/latest/

import requests

import json

Line 772:

def submitEvent(url_path,params):

r = requests.post(url_path, data=json.dumps(params))

print(r.text+" : Event Submitted")</~~lang~~>

print(r.text+" : Event Submitted")</syntaxhighlight>

main.py

<~~lang~~ python>import eventGetter as eg

<syntaxhighlight lang="python">import eventGetter as eg

import json

Line 890:

main()</~~lang~~>

main()</syntaxhighlight>

=={{header|Wren}}==

Line 900:

I did wonder whether it was worth the effort to do this task given that we're using a deprecated API and can't test creating events without a paid subscription which I don't have. However, from Wren's viewpoint, there are some points of interest relating to the use of WrenGo - notably passing Wren maps to Go - which may be a useful reference for the future.

<~~lang~~ ecmascript>/* meetup.wren */

<syntaxhighlight lang="ecmascript">/* meetup.wren */

import "./date" for Date

Line 991:

// delete the event just posted

c.deleteEvent(event.eventId)

System.print("The %(event.eventName) event has been cancelled.\n")</~~lang~~>

System.print("The %(event.eventName) event has been cancelled.\n")</syntaxhighlight>

We now embed this in the following Go program and build it. To run it, you will need the necessary authorization, a paid subscription and, of course, non-fictitious data.

<~~lang~~ go>/* go build meetup.go */

<syntaxhighlight lang="go">/* go build meetup.go */

package main

Line 1,241:

vm.InterpretFile(fileName)

vm.Free()

}</~~lang~~>

}</syntaxhighlight>