Use the Narwhal API in Zapier

What you'll set up

Zapier connects a scheduled trigger to actions that request data and use the response. You'll end up with a Zap that calls Narwhal and passes the fields you need to an email, a Slack action or a sheet row. Narwhal uses one account and one API key across its data APIs; REST and MCP share that key. Webhooks by Zapier is a premium Zapier app, so check that your Zapier plan includes Webhooks by Zapier before setting up the request.

Set your API key

1. Create a free key Get a free key at narwhalapi.com/signup. Use that key for the Narwhal requests in your Zap, whichever data area you select.
2. Store the key Keep the key in an environment variable called NARWHAL_API_KEY. The request header needs the key's value, with Bearer before it.
3. Add the request header In Webhooks by Zapier, use Custom Request with GET and add the header Authorization: Bearer YOUR_KEY. Replace YOUR_KEY with your Narwhal key; the URLs use the base https://api.narwhalapi.com.

Pull data without code

1. Add the scheduled trigger Use Schedule by Zapier as the trigger. Set it to run every day or every hour, according to how often you want the data sent to later actions.
2. Add the data request Add Webhooks by Zapier and use Custom Request with GET. Enter the URL for the area you want and the Authorization header; the request settings here pair each URL with the response field to use.
3. Use the returned fields Add an email, Slack or sheet row action and map the returned fields by name. For example, the commodity response has price, while the holiday response has holidays.
4. Handle lists of rows When rows arrive in a list field, add a Looping or Formatter step to handle one row at a time. Use that row's fields in the action that needs them, such as the holiday date and name in a sheet row.

Header: Authorization: Bearer YOUR_KEY

Holidays    GET https://api.narwhalapi.com/v1/calendars/holidays/USA/2026               (field: holidays)
Releases    GET https://api.narwhalapi.com/v1/economics/calendar?countries=USA&start_date=2026-11-01&end_date=2026-11-30&limit=100   (field: releases)
Economics   GET https://api.narwhalapi.com/v1/economics/USA/cpi/observations?start=2025-09  (field: observations)
Commodity   GET https://api.narwhalapi.com/v1/commodities/spot/BRENT/USD                 (field: price)
FX          GET https://api.narwhalapi.com/v1/fx/rates/USD?currencies=EUR,IDR           (field: rates)
Predictions GET https://api.narwhalapi.com/v1/predictions/policy-paths/federal-reserve   (field: meetings)

Run it on a schedule

Schedule by Zapier can trigger the request every day or every hour. The trigger sets when the Zap asks Narwhal for data, and the following actions use the fields returned by that request. Set the schedule for the data you want to pass into email, Slack or a sheet row.

Holidays in Zapier

The holiday request returns holidays for USA in 2026. Each holiday has date and name, which you can use together in a later action. To put individual holidays into sheet rows, handle the holidays list one row at a time with a Looping or Formatter step before mapping those fields.

Method: GET
URL: https://api.narwhalapi.com/v1/calendars/holidays/USA/2026
Header: Authorization: Bearer YOUR_KEY
Read field: holidays

Release dates in Zapier

The economic calendar request returns releases for USA during November 2026. Each release has at, period, topic and status. Use those fields when the action needs a release date and its context, and handle the releases list one row at a time if you want a separate action for each release. The calendar provides release dates, while the economics request uses observations with periods and values. Select the calendar URL when the fields your action needs are the release time, topic or status.

Method: GET
URL: https://api.narwhalapi.com/v1/economics/calendar?countries=USA&start_date=2026-11-01&end_date=2026-11-30&limit=100
Header: Authorization: Bearer YOUR_KEY
Read field: releases

Economics in Zapier

The CPI request asks for USA observations starting in September 2025 and returns observations. Each observation has period and value. Map both fields into your action when you need the value alongside the period it describes; use a Looping or Formatter step to handle the observations one row at a time. Narwhal economics includes CPI, inflation, GDP and yields; this request uses CPI.

Method: GET
URL: https://api.narwhalapi.com/v1/economics/USA/cpi/observations?start=2025-09
Header: Authorization: Bearer YOUR_KEY
Read field: observations

If the start date is earlier than your plan's history window, Narwhal moves it up to the window's first day with no error. The response then begins later than you asked. 403 plan_upgrade_required applies when the whole range ends before that window, or when you read a single date or period outside it.

Commodities in Zapier

The commodity request reads the Brent spot price in USD from price. Map that field into the email, Slack or sheet row action that needs the price. Commodity spot codes include, for example, XAU, XAG, XPT, XPD, XCU, BRENT and WTI; this request uses BRENT with USD in the URL.

Method: GET
URL: https://api.narwhalapi.com/v1/commodities/spot/BRENT/USD
Header: Authorization: Bearer YOUR_KEY
Read field: price

FX in Zapier

The exchange-rate request uses USD as the base and asks for EUR and IDR. Read rates, where each entry has currency and rate. Handle the list one row at a time to pass each currency and its rate into a later action, with the currency field identifying which rate the action receives.

Method: GET
URL: https://api.narwhalapi.com/v1/fx/rates/USD?currencies=EUR,IDR
Header: Authorization: Bearer YOUR_KEY
Read field: rates

Predictions in Zapier

The Federal Reserve policy-path request returns meetings. Each meeting has resolves_at, p_cut, p_hold and p_hike. Use the meeting's resolution time alongside its cut, hold and hike probabilities in a later action; handle the meetings list one row at a time when you want to use each meeting separately.

Method: GET
URL: https://api.narwhalapi.com/v1/predictions/policy-paths/federal-reserve
Header: Authorization: Bearer YOUR_KEY
Read field: meetings

Can Zapier receive Narwhal webhooks?

Yes. A Catch Hook URL from Zapier can be a Narwhal webhook destination. Narwhal webhooks are on Basic or Pro; Free has 0 destinations. A scheduled GET Zap asks Narwhal for data; a Catch Hook receives a webhook sent to its URL.

Why does a Zap use so many requests?

Each GET request uses your Narwhal quota, so an hourly Zap calling six URLs uses 144 requests a day and 4,320 a month. Count the URLs the Zap calls as well as how often the trigger fires. A Zap that requests several data areas makes a request for each URL, even when later actions use the fields together in the same email or sheet row.