Create TeamAdd Your APIDocs
Log In
Sign Up
Rapid account: Michael Mogley

Michael Mogley / wirefreethought

    Discussions

    430
    Title
    		Created at (Click to sort ascending)
    A
    1
    		 Sorry for the late reply. RapidAPI did not send me a new-thread notification. Yes you will get back all known countries, but you still need to page results. The way to page them is to use **offset** in combination with **limit**. For example, first 5 results: `GET /v1/geo/countries?offset=0&limit=5` Next 5 results: `GET /v1/geo/countries?offset=5&limit=5` If you want to set a higher **limit** to get back more results in a single page, you'll need to upgrade to the PRO plan (which currently offers a max **limit** = 100). Sun 6:04 26/5/24
    A
    1
    		 Sorry for the late reply. RapidAPI did not send me a new-thread notification. Currently there is no smaller population unit below **CITY**. So you will have to rely on the **minPopulation** param to filter the results as you describe. **minPopulation** should work to exclude places with populations below the specified min. This would be the only way to exclude smaller populated areas such as the ones you list. What's the specific request you're trying to make? Sun 6:01 26/5/24
    A
    1
    		 Hi sorry for the late reply. I didn't receive a notification for your question and just seeing it now. *Is there an API available that supports fetching regions based on multiple country IDs, and similarly, fetching cities based on multiple country IDs and region IDs?* The short answer is not currently. However, it IS possible to fetch cities/places for specific country IDs. *Is there a method to augment the response with additional details? For instance, when obtaining regions for a selected country, can we include the country code in the response for easier reference? .Thank you* Not in the REST API. However, you DO have this flexibilty in the GraphQL variant. See https://rapidapi.com/wirefreethought/api/geodb-cities-graphql Sun 5:15 7/4/24
    A
    1
    		 Hi sorry for the late reply. I didn't receive a notification for your question and just seeing it now. All results are paged. To see the next page of results in your case, you need to bump the offset param. For example, for page 2: GET /v1/geo/countries?offset=10&limit=10 Sun 5:08 7/4/24
    A
    1
    		 Hi sorry for the late reply. I didn't receive a notification for your question and just seeing it now. Are you still having these issues? If you're on the basic plan, you are being rate-limited. You should upgrade to a paid plan for production use. Sun 5:07 7/4/24
    A
    1
    		 Hi sorry for the late reply. I didn’t receive a notification for your question and just seeing it now. Every country/region/city/place endpoint takes an optional **languageCode** param which currently can have one of the following values: * **de** (German) * **en** (English - DEFAULT) * **es** (Spanish) * **fr** (French) * **it** (Italian) * **ru** (Russian) * **pt** (Portuguese) * **pt_BR** (Portuguese - Brazil) For example, to get cities in French: GET /v/geo/places?types=CITY&languageCode=fr Note that results in languages other than English are currently not fully guaranteed, but they should exist for major cities. In cases where the requested language translation isn't available, the service will default the result to English. Sun 5:00 7/4/24