Airtable does not provide static IP addresses that you can whitelist.

Instead, you can make all of your API calls by using Make's advanced integrations & automations which publicly publishes their list of IP addresses that you should whitelist.

Not only does Make natively support Airtable (and thousands of other apps), but you can also craft your own custom API calls to any API that you’d like by using their Make's HTTP module.

If you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is one of the ways that you could instantly trigger a Make automation from Airtable. 

I also give live demonstrations of how to use Make in many of my Airtable podcast appearances. For example, in this video, I show how to work with Airtable arrays in Make.

Hope this helps!

If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Can you please provide more details about which feature of Airtable you are using? Are you using Automations or Scripts or Sync to trigger API requests? Which bank service platform are you attempting to integrate? We have integrated thousands of banks at Fintable, we may be able to help.

I'm facing the same issue, when trying to reach our dataserver using Fetch in a script within Automations.

We whitelisted the IPs as described in this guide (firewall allowlist settings) sadly without result.
I should add our server is not Jira, but I would think the principle remains the same of whitelisting Airtable's IPs.

Does anyone know which IPs Airtable is using for requests originating from scripts within Automations?

Airtable doesn’t provide fixed IP addresses for API requests, so you’ll need to use a proxy or middleware server if your system requires IP whitelisting.

Airtable doesn’t provide static IP addresses for API requests, so if you need IP whitelisting, an external solution is required. You can use a proxy or middleware server with ipv6 proxies being a particularly robust option. LightningProxies offers IPv6 proxies with vast subnet diversity (including /29 subnets), support for both HTTP and SOCKS5 protocols, unlimited threads, and flexible speeds perfect for handling scalable API traffic reliably and efficiently.