Created
November 27, 2020 23:38
-
-
Save KevDev90/7c8449edf9ad7b5f7313ddb9bb81aea6 to your computer and use it in GitHub Desktop.
Reading api documentation assignment 2
This file contains hidden or 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
| 1.Does this API require authentication? | |
| Most requests must be authenticated. Unless otherwise specified, response payloads are returned in JSON format. | |
| 2.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. | |
| 3.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.) | |
| GET /find/groups - contains many properties such as approved: boolean, category: '', city '' etc.. that all provide additional | |
| attributes to search events through. | |
| 4.What are the limitations placed on the number of requests that can be made? | |
| Clients that issue too many requests in a short period of time will receive a HTTP 429 error and an error message. | |
| 5.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 Error 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