Created
December 10, 2019 23:30
-
-
Save peyo/f09385b19dfd4d8b2935d529e8e100dd to your computer and use it in GitHub Desktop.
Reviewing the meetup API
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
https://www.meetup.com/meetup_api/ | |
Does this API require authentication? | |
- Yes. Info to authenticate is available here: https://www.meetup.com/meetup_api/auth/ | |
Does this API support CORS? | |
- "The Meetup API supports the CORS specification which allows browser clients hosted on a domain other than api.meetup.com to communicate directly with the API." | |
Find the events search endpoint documentation. Describe in detail the response format of the events search endpoint. (HINT: You may need other keywords to find this endpoint.) | |
- https://api.meetup.com/find/upcoming_events | |
The response is provided in two major details, by city and events. There are a lot of objects return for both city and events categories. To name a few, for city, city (name of city), country (country code), id, lat, lon, member_count, name-string, state, zip. For events, attendance_count(?), attendance_sample, rsvpable, and rsvp_rules, to name a few. | |
- What are the limitations placed on the number of requests that can be made? | |
There is a maximum number of requests that can be made in a given time frame. | |
- List the errors that you can expect when making calls to this API. | |
400 bad request - "when there was a problem with the request" | |
401 unauthorized - "when you don't provide a valid token" | |
429 too many requests - "when you've gone over your request rate limit" | |
500 internal server errorb - "an unexpected error occured on our servers" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment