Use the Narwhal API in Make

What you'll set up

Make uses an HTTP module to request data from Narwhal API and pass parsed fields into later modules. You will have a scenario with a GET request, an Authorization header and response parsing, plus scheduling on the first module. Narwhal uses one account and one API key across its data APIs; REST and MCP share that key. The base URL for the requests is https://api.narwhalapi.com. The economics API includes CPI, inflation, GDP and yields. The economic calendar supplies release dates, and the CPI observations request below supplies periods and values.

Set your API key

1. Create a free key Get a free API key at narwhalapi.com/signup. Use that key for the Narwhal requests you add to your Make scenario, including requests for different data areas.
2. Keep the key in an environment variable Keep your key in an environment variable called NARWHAL_API_KEY. The request settings use YOUR_KEY as a placeholder; replace it with your key when you enter the Authorization header in Make.
3. Set the request header Use Authorization as the header name and Bearer YOUR_KEY as its value. Keep the Bearer prefix when you replace the placeholder, and use the same header for each of the GET requests below.

Pull data without code

1. Add the HTTP module In your scenario, add the HTTP module and use Make a request. Set the method to GET and enter the URL for the data area you want to pull. For the Brent example, the URL is https://api.narwhalapi.com/v1/commodities/spot/BRENT/USD; it uses the same header and parsing settings as the list requests.
2. Enter the request settings Add the Authorization header with your key and set Parse response to Yes. For requests with query parameters, use the values in the settings below, such as the country and date range for release dates.
3. Map the response fields Map the parsed fields into later modules. Use an Iterator on the list field for holidays, releases, observations, rates or meetings; map Brent’s data.price field directly.

These are the HTTP module settings for each area. The releases, economics and FX requests include query string values alongside the endpoint. Keep those values with their request when you enter the URL and query settings in Make.

Headers: Authorization = Bearer YOUR_KEY     Parse response: Yes

Holidays    GET https://api.narwhalapi.com/v1/calendars/holidays/USA/2026
            Iterator on: data.holidays          fields: date, name
Releases    GET https://api.narwhalapi.com/v1/economics/calendar
            Query string: countries=USA, start_date=2026-11-01, end_date=2026-11-30, limit=100
            Iterator on: data.releases          fields: at, topic, status
Economics   GET https://api.narwhalapi.com/v1/economics/USA/cpi/observations   Query string: start=2025-09
            Iterator on: data.observations      fields: period, value
Commodity   GET https://api.narwhalapi.com/v1/commodities/spot/BRENT/USD
            map: data.price
FX          GET https://api.narwhalapi.com/v1/fx/rates/USD   Query string: currencies=EUR,IDR
            Iterator on: data.rates             fields: currency, rate
Predictions GET https://api.narwhalapi.com/v1/predictions/policy-paths/federal-reserve
            Iterator on: data.meetings          fields: resolves_at, p_hold

Run it on a schedule

Open scenario scheduling on the first module using its clock icon. Set the scenario to run every N minutes or at set times. The schedule belongs to the scenario’s first module, while the HTTP module holds the GET method, URL, header and Parse response setting. For a daily pull, use the set-times scheduling option; schedule a daily data pull has the related workflow.

Holidays in Make

Request USA holidays for 2026 and use the holidays list. Each holiday has a date and a name, so both fields can be mapped into later modules. The year and country are part of this request’s URL. Put the Iterator on data.holidays and select the holiday fields from its output when you configure the modules that follow. When you map the holiday name, use the date from that same holiday item alongside it.

Headers: Authorization = Bearer YOUR_KEY     Parse response: Yes
Holidays    GET https://api.narwhalapi.com/v1/calendars/holidays/USA/2026
            Iterator on: data.holidays          fields: date, name

Release dates in Make

Use the economic calendar for USA release dates from November 2026. The request sets start_date to 2026-11-01, end_date to 2026-11-30 and limit to 100. Each release has at, period, topic and status fields. The sample maps the release time, topic and status from data.releases; the period is also available on each release if a later module needs it.

Headers: Authorization = Bearer YOUR_KEY     Parse response: Yes
Releases    GET https://api.narwhalapi.com/v1/economics/calendar
            Query string: countries=USA, start_date=2026-11-01, end_date=2026-11-30, limit=100
            Iterator on: data.releases          fields: at, topic, status

Economics in Make

Request USA CPI observations with start=2025-09 in the query string. The response has an observations list with a period and a value for each observation. Map both fields from the Iterator output when a later module needs the CPI value together with its period. Use data.observations as the Iterator’s list field for this request.

Headers: Authorization = Bearer YOUR_KEY     Parse response: Yes
Economics   GET https://api.narwhalapi.com/v1/economics/USA/cpi/observations   Query string: start=2025-09
            Iterator on: data.observations      fields: period, value

Commodity spot prices in Make

Pull the Brent spot price in USD with the commodity request. Its response has a single price field, which you can map into a later module as data.price. This request uses BRENT as the spot code and USD in the URL. Commodity spot codes include, for example, XAU, XAG, XPT, XPD, XCU, BRENT and WTI.

Headers: Authorization = Bearer YOUR_KEY     Parse response: Yes
Commodity   GET https://api.narwhalapi.com/v1/commodities/spot/BRENT/USD
            map: data.price

Exchange rates in Make

Request EUR and IDR exchange rates with USD in the endpoint and currencies=EUR,IDR in the query string. The response’s rates list has currency and rate fields. Keep the currency field with its rate when you map the Iterator output into a later module, so the mapped value retains the currency returned with it. In the sample, EUR and IDR are requested together, and the Iterator uses the data.rates list returned by that request.

Headers: Authorization = Bearer YOUR_KEY     Parse response: Yes
FX          GET https://api.narwhalapi.com/v1/fx/rates/USD   Query string: currencies=EUR,IDR
            Iterator on: data.rates             fields: currency, rate

Prediction-market odds in Make

Use the Federal Reserve policy-path request to pull the meetings list. Each meeting has resolves_at, p_cut, p_hold and p_hike fields. The sample selects resolves_at and p_hold from the Iterator output. You can also map p_cut and p_hike from that meeting when a later module needs those fields alongside the hold probability.

Headers: Authorization = Bearer YOUR_KEY     Parse response: Yes
Predictions GET https://api.narwhalapi.com/v1/predictions/policy-paths/federal-reserve
            Iterator on: data.meetings          fields: resolves_at, p_hold

How do I read the list?

With Parse response on, the list appears under data. An Iterator turns that list into one item per row. Set the Iterator to the list field itself, such as data.releases, then map the fields on each item into later modules.

How many operations does a run use?

Make uses one operation per module run, and quotas are set on the Make side. Count the module runs when you consider the operations used by your scenario’s schedule.