This API provides **real-time elevation and current weather data** for any location worldwide using a place name, address, or geographic coordinates (latitude & longitude). ---

Getting Started

To begin using this API, follow these steps and make your first API call: **Subscribe to a plan:** Visit our Pricing page and subscribe to one of the available plans. If you are just starting, you can subscribe to the free **BASIC plan** of the API (hard-limited and no credit card required). **Make your first API call:** Visit the RapidAPI Playground. The default endpoint will already be selected and displayed on the main panel view. Since there is a default query parameter value, simply click the blue **“Test endpoint”** button to make your first API call. The JSON response will be displayed on the right panel. **Documentation and Resources:** Refer to the detailed endpoint descriptions, parameters, and examples provided in the **Endpoints** tab. Code snippets are available for all popular programming languages and environments, including JavaScript, Python, Java, Shell, and more, to help you easily integrate the API into your project or workflow. You should be good to go now! ---

Authentication

To authenticate with the API, send the following headers with every request: * **X-RapidAPI-Host** * **X-RapidAPI-Key** (your RapidAPI App API Key) These headers are automatically included when testing endpoints from the RapidAPI Playground and are shown in the provided code snippets. ---

Input Parameters

The following query parameters are supported by the API: query (required)
City name or location for which elevation and weather information is retrieved.
Example: New York, London, Tokyo lat (optional)
Latitude coordinate of the location. Used if you prefer to specify location by coordinates instead of city name.
Format: decimal degrees
Example: 40.7128, 51.5074 lon (optional)
Longitude coordinate of the location. Must be provided together with lat if using coordinates.
Format: decimal degrees
Example: -74.0060, -0.1278 ---

Response Structure

Here’s an example of a successful response: ``` { "success": true, "location": "Mount Everest, Solukhumbu, Nepal", "coordinates": { "latitude": 27.9881, "longitude": 86.925 }, "elevation": { "meters": 8848, "feet": 29029.53 }, "weather": { "temperature_c": -12.4, "windspeed_kmh": 38.7, "wind_direction": 270, "condition": "Clear sky", "time": "2025-12-23T11:00" }, } ``` Please note that some errors might be returned by the RapidAPI gateway and will have a different structure. Refer to the **Error Handling / Error Response Structure** section for more details. In addition, RapidAPI adds several headers to each response. For more information, please refer to the RapidAPI documentation on response headers. ---

Endpoints

This API provides a single endpoint that allows you to retrieve elevation and current weather data using either: * A **place name / address** (e.g. `Mount Everest`, `New York City`) * **Latitude & longitude coordinates** For detailed endpoint parameters, responses, examples, and to try the API live, please refer to the **Endpoints** section of the API. ---

Rate Limiting

Each subscription plan defines the maximum number of requests permitted per month, along with a rate limit expressed in RPS (Requests Per Second). Please note that all free plans (e.g. BASIC) are rate-limited to **1000 requests per hour**, as required by RapidAPI. ---

Rate Limits Headers

All API responses include rate limit information in the following headers: **x-ratelimit-requests-limit** The maximum number of requests allowed under your current subscription plan. **x-ratelimit-requests-remaining** The number of requests remaining before you reach your quota limit. This value resets daily or monthly, depending on your plan configuration. **x-ratelimit-requests-reset** The number of seconds remaining until your quota resets. You can view your limits and quotas on the API’s Pricing page in the RapidAPI Hub. ---

Handling Limits

When you exceed your rate limit, the RapidAPI gateway will return a **429 Too Many Requests** error. When this occurs, wait until the rate limit resets or consider upgrading your subscription plan for higher limits. Example error response: ``` { "message": "Too many requests" } ``` ---

Code Examples

Code examples for popular programming languages and environments (JavaScript, Python, Java, Shell, etc.) are available in the **Endpoints** tab under the **Code Snippets** section. ---

Common HTTP Status Codes

**400 Bad Request** Returned when required parameters are missing or invalid (e.g. missing location or invalid coordinates). **403 Forbidden** Indicates that you are not subscribed to the API or your API key is invalid. **404 Not Found** Returned when the requested location cannot be resolved. **429 Too Many Requests** Indicates that you have exceeded your rate limit. **5XX Server Error (500, 502, 503)** Indicates a temporary server or upstream service issue. These errors are rare and usually resolve automatically. ---

Support

If you encounter any issues you cannot resolve or need further clarification, please contact us with the error code, message, and request details. We’ll be happy to assist you. ---

Contact Us

For custom plans, high-volume usage, enterprise solutions, or other inquiries, feel free to reach out: **Email:** [alreadycoded@gmail.com](mailto:alreadycoded@gmail.com) **Website:** [https://www.alreadycoded.com](https://www.alreadycoded.com)