Use a REST API: Difference between revisions

Line 3:

<ol>

<li>~~Get~~ a list of events</li>

<li>Create a 'get' function for the API, that can be used to get a list of events for example.</li>

<li>Create a 'post' function for the API, that can be used to create a new venue or event for example.</li>

<li>Submit events</li>

</ol>

Using the [http://www.meetup.com/meetup_api/ Meetup.com API].

Both functions take two parameters, 'details' and 'url'. Details is an object containing required and optional arguments specified by the API's requirement (Example, [http://www.meetup.com/meetup_api/docs/2/open_events/ open events] requires at least one detail). The 'url' supplied informs the get/post method what part of the API to ping (Example, valid URLs for 'get' could be ['/2/open_events' http://www.meetup.com/meetup_api/docs/2/open_events/] or ['/comments' http://www.meetup.com/meetup_api/docs/comments/]).

Some posting features are paid, such as creating an event. [Editing member details http://www.meetup.com/meetup_api/docs/2/member/#edit] for example, is an example of a free 'post' API.

An API key is assumed to be supplied through an <code>api_key.txt</code> file.

Line 13:

Line 17:

Solutions should be implemented without any meetup.com helper libraries, to make it easier to translate to languages which don't have such helper libraries. However, examples that do use helper libraries may be provided as an addition.

This task was created through [https://www.google-melange.com/gci/task/view/google/gci2014/5820245222621184 Google Code-in]

This task was created through [https://www.google-melange.com/gci/task/view/google/gci2014/5820245222621184 Google Code-in].

=={{header|Go}}==