Fixer

Fixer API is capable of delivering real-time exchange rate data for 170 world currencies.

Power end-to-end data operations for your Fixer API with Nexla. Our bi-directional Fixer connector is purpose-built for Fixer, 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 Fixer or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Fixer 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 a Fixer credential, you need to obtain an API key from your Fixer account. The API key is required to authenticate with the Fixer API.

To obtain your API key, you need to have a Fixer account with API access enabled. Once you have access to your account, you can generate an API key from your Fixer dashboard. The API key is sent as the access_key query parameter for all API requests to the Fixer API. For detailed information about API key setup and authentication, refer to the Fixer API documentation.

Authenticate

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 – Fixer

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 Fixer API key. This is the key you generated from your Fixer dashboard, as described in Prerequisites. The API key is sent as the access_key query parameter for all API requests to the Fixer API.

   Keep your API key secure and do not share it publicly. The API key provides access to your Fixer account and should be treated as sensitive information. You can view and manage your API keys in your Fixer dashboard. For detailed information about obtaining and managing API keys, see the Fixer 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 Fixer connector tile, then select the credential that will be used to connect to the Fixer instance, and click Next; or, create a new Fixer 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 Fixer 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.

Get Latest Rates

Get the latest currency exchange rates. Depending on your subscription plan, the API's latest endpoint will return real-time exchange rate data updated every 60 minutes, every 10 minutes, or every 60 seconds.

• Enter the three-letter currency code of your preferred base currency in the Base currency field. This is the currency against which all other currencies will be quoted. The default value is empty if not specified, which means the API will use EUR as the base currency.

• Enter a list of comma-separated currency codes to limit output currencies in the Symbols field. This allows you to specify which currencies you want to retrieve exchange rates for. The default value is EUR,USD,GBP,JPY if not specified.

• The endpoint uses GET requests to https://data.fixer.io/api/latest?base={base}&symbols={symbols} where {base} is the Base currency you provide and {symbols} is the Symbols you provide. The endpoint URL is automatically constructed based on the Fixer API base URL, the base currency, and the symbols.
• The endpoint does not use pagination and returns the latest exchange rates in a single request.
• The endpoint will return the latest exchange rates for the specified base currency and symbols. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.

Currency codes should follow the ISO 4217 standard (e.g., USD, EUR, GBP, JPY). The base currency determines the currency against which all other currencies are quoted. If no base currency is specified, EUR is used as the default. The Symbols parameter allows you to limit the response to specific currencies, which can improve performance and reduce data transfer. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about getting latest rates, see the Fixer API documentation.

Get time-series data

If supported by your subscription plan, the Fixer API's timeseries endpoint lets you query the API for daily historical rates between two dates of your choice, with a maximum time frame of 365 days.

• Enter the start date of your preferred timeframe in the Start date field. This must be a valid date in the format YYYY-MM-DD. You can use Nexla macros like {now-1} for yesterday or {now-7} for 7 days ago. The default value is {now-1} (yesterday) if not specified.

• Enter the end date of your preferred timeframe in the End Date field. This must be a valid date in the format YYYY-MM-DD. You can use Nexla macros like {now} for today. The default value is {now} (today) if not specified.

• Enter the three-letter currency code of your preferred base currency in the Base currency field. This is the currency against which all other currencies will be quoted. The default value is empty if not specified, which means the API will use EUR as the base currency.

• Enter a list of comma-separated currency codes to limit output currencies in the Symbols field. This allows you to specify which currencies you want to retrieve exchange rates for. The default value is EUR,USD,GBP,JPY if not specified.

• The endpoint uses GET requests to https://data.fixer.io/api/timeseries?from={start_date}&to={end_date}&base={base}&symbols={symbols} where {start_date} is the Start date, {end_date} is the End Date, {base} is the Base currency, and {symbols} is the Symbols you provide. The endpoint URL is automatically constructed based on the Fixer API base URL and all the parameters.
• The endpoint does not use pagination and returns all historical rates for the specified date range in a single request.
• The endpoint will return daily historical exchange rates for the specified date range, base currency, and symbols. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.

The time-series endpoint requires a subscription plan that supports historical data access. The maximum time frame for a single query is 365 days. Date values must be in the format YYYY-MM-DD. Currency codes should follow the ISO 4217 standard (e.g., USD, EUR, GBP, JPY). The base currency determines the currency against which all other currencies are quoted. If no base currency is specified, EUR is used as the default. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about getting time-series data, see the Fixer 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

Fixer data sources can also be manually configured to ingest data from any valid Fixer API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. 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.

Fixer API endpoints typically follow the pattern https://data.fixer.io/api/{endpoint_path}. The endpoint requires API Key authentication via the access_key query parameter, which is handled automatically by your credential configuration. For detailed information about available Fixer API endpoints, see the Fixer API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Fixer data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.