OpenWeather

OpenWeather provides comprehensive weather data services through reliable APIs, offering current weather conditions, forecasts, historical data, and weather maps for businesses and developers to integrate accurate meteorological information into their applications and services.

Power end-to-end data operations for your OpenWeather API with Nexla. Our bi-directional OpenWeather connector is purpose-built for OpenWeather, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to OpenWeather or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your OpenWeather workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an OpenWeather API credential, you need to obtain your API key from your OpenWeather account. OpenWeather uses API key authentication for all API requests, with the API key sent as a query parameter (appid) in the API request URL.

To obtain your OpenWeather API key, follow these steps:

1. Sign in to your OpenWeather account, or create a new account at OpenWeather.

2. Navigate to your account dashboard or profile settings in the OpenWeather interface.

3. Look for the API keys or API section in your account settings or dashboard.

4. If you don't have an API key yet, click Generate API Key or Create API Key to create a new API key.

5. Configure your API key settings:

   • Enter a name or description for the API key (e.g., "Nexla Integration")
   • Review and select the API subscription plan or usage limits for the key

6. Click Generate or Create to create the API key.

7. Copy the API key immediately after it's generated, as it may not be accessible again after you navigate away from the page.

8. Store the API key securely, as you will need it to configure your Nexla credential. The API key is sensitive information and should be kept confidential.

The API key is sent as a query parameter (appid) in the API request URL for all API requests to the OpenWeather API (e.g., https://api.openweathermap.org/data/2.5/weather?appid={api_key}&q=San+Francisco). The API key authenticates your requests and grants access to OpenWeather resources based on your account plan and usage limits. If your API key is compromised, you should immediately regenerate it in your OpenWeather account settings and update your credential. For detailed information about obtaining API keys, API authentication, and available endpoints, refer to the OpenWeather API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	No	Yes	OpenWeather API Key

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – OpenWeather

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your OpenWeather API key in the API Key field. This is the API key you obtained from your OpenWeather account settings (API keys section). The API key is sent as a query parameter (appid) in the API request URL for all API requests to the OpenWeather API. The API key is sensitive information and must be kept confidential.

   Your OpenWeather API key can be found in your OpenWeather account settings under the API keys section. The API key is sent as a query parameter (appid) in the API request URL for all API requests to the OpenWeather API (e.g., https://api.openweathermap.org/data/2.5/weather?appid={api_key}&q=San+Francisco).

   If your API key is compromised, you should immediately regenerate it in your OpenWeather account settings and update your credential. The API key provides access to your OpenWeather account and should be treated as sensitive information. Keep your API key secure and do not share it publicly.

   For detailed information about obtaining API keys, API authentication, and available endpoints, see the OpenWeather API documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the OpenWeather connector tile, then select the credential that will be used to connect to your OpenWeather account, and click Next; or, create a new OpenWeather API credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common OpenWeather API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Current Weather for City Name

This endpoint template fetches current weather data for one location by city name from the OpenWeather API. Use this template when you need to retrieve current weather conditions, temperature, humidity, wind speed, and other weather metrics for a specific city. You can call by city name or city name, state and country code. API responds with a list of results that match a searching word.

• Enter the city name in the City Name field. This should be the name of the city for which you want to fetch current weather data (e.g., London, New York, San Francisco). You can also include state and country code for more specific results (e.g., London, GB, New York, NY, US). The city name is used as a query parameter in the API request.

This endpoint fetches current weather data for a specific location by city name. The API responds with a list of results that match the searching word, so you may receive multiple results if the city name matches multiple locations. The endpoint returns current weather conditions including temperature, humidity, wind speed, pressure, visibility, and weather descriptions.

For detailed information about current weather data, API response structures, available weather metrics, and location search options, see the OpenWeather API documentation.

Current Weather for City Id

This endpoint template fetches current weather data for one location by City ID from the OpenWeather API. Use this template when you need to retrieve current weather conditions for a specific city using its unique City ID, which provides exact results without ambiguity.

• Enter the city ID in the City Id field. This should be the unique identifier of the city for which you want to fetch current weather data. The City ID is a numeric identifier assigned by OpenWeather to each city, providing exact location matching. Refer to the OpenWeather API documentation for City ID lists.

This endpoint fetches current weather data for a specific location by City ID. The API responds with exact results for the specified City ID, eliminating ambiguity that may occur with city name searches. The endpoint returns current weather conditions including temperature, humidity, wind speed, pressure, visibility, and weather descriptions.

For detailed information about current weather data, City ID lists, API response structures, and available weather metrics, see the OpenWeather API documentation.

Current Weather for Geographic Coordinates

This endpoint template fetches current weather data for one location by geographic coordinates (latitude and longitude) from the OpenWeather API. Use this template when you need to retrieve current weather conditions for a specific location using its precise geographic coordinates.

• Enter the latitude in the Latitude field. This should be the latitude coordinate of the location for which you want to fetch current weather data (e.g., 37.7749 for San Francisco). The latitude must be a valid decimal number between -90 and 90.
• Enter the longitude in the Longitude field. This should be the longitude coordinate of the location for which you want to fetch current weather data (e.g., -122.4194 for San Francisco). The longitude must be a valid decimal number between -180 and 180.

This endpoint fetches current weather data for a specific location by geographic coordinates. The API responds with exact results for the specified latitude and longitude coordinates, providing precise location matching. The endpoint returns current weather conditions including temperature, humidity, wind speed, pressure, visibility, and weather descriptions.

For detailed information about current weather data, geographic coordinates, API response structures, and available weather metrics, see the OpenWeather API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

OpenWeather API data sources can also be manually configured to ingest data from any valid OpenWeather API endpoint, including endpoints not covered by the pre-built templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

OpenWeather API typically uses the GET method, and requests must include your API key as the appid query parameter in the endpoint URL (e.g., https://api.openweathermap.org/data/2.5/weather?appid={api_key}&q=London). For the Response Data Path, use $ to extract the entire response object, since OpenWeather API responses typically return a single weather data object per request.

Once all of the relevant settings have been configured, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the data source configuration for later use.