topic Re: Meraki Group Policy L3 API Question in Network Platform API

Meraki Group Policy L3 API Question

rodney2 — Tue, 03 Jun 2025 02:15:32 GMT

Hi everyone,

I’m working on a script that needs to add L3 firewall rules under a group policy, and I’m wondering if there’s any support for including a `source` field in the request payload. I couldn’t find any mention of this in the official documentation, but I’m curious if it’s supported unofficially or possibly planned for a future release.

According to the documentation, the schema for `L3FirewallRules` is as follows:

- `L3FirewallRules`: `object[]`

An ordered array of the L3 firewall rules

- `comment`: `string` — Description of the rule (optional)

- `destCidr*`: `string` — Destination IP address (IP, CIDR, FQDN, or 'any')

- `destPort`: `string` — Destination port (1–65535, range, or 'any')

- `policy*`: `string` — 'allow' or 'deny'

- `protocol*`: `string` — 'tcp', 'udp', 'icmp', 'icmp6', or 'any'

As you can see, there’s no mention of a `source` field. Has anyone tried including it anyway, or received clarification from the dev team?

Any insights would be greatly appreciated!

Thanks in advance!

Re: Meraki Group Policy L3 API Question

Raphael_L — Tue, 03 Jun 2025 03:08:04 GMT

Hi ,

You can't add sources to the group policies since they are already applied to a source ( either a client / vlan ).

You have the same behavior directly on the dashboard.

Re: Meraki Group Policy L3 API Question

rodney2 — Tue, 03 Jun 2025 05:48:56 GMT

But why in this screenshot(captured from the dashboard). It allows to define the source as well.

Re: Meraki Group Policy L3 API Question

aleabrahao — Tue, 03 Jun 2025 10:56:52 GMT

Where did you get this screenshot from? From the internet or from your dashboard?

I agree with Raphael on this one, as far as I know it is not possible to specify the source.

Re: Meraki Group Policy L3 API Question

Rasmus Hoffmann Birkelund — Tue, 03 Jun 2025 10:58:32 GMT

Where do you have that screenshot from, because there's no source field on my lab network.

Re: Meraki Group Policy L3 API Question

matt_uc — Tue, 03 Jun 2025 16:03:48 GMT

The Source field is only available if you are using AD integration, per Meraki documentation.

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies

Note: Source IP addresses on layer 3 firewall rules are only configurable on WAN Appliance when active directory integration is enabled.

Re: Meraki Group Policy L3 API Question

aleabrahao — Tue, 03 Jun 2025 16:16:29 GMT

@matt_ucis right, I just tested it.

Re: Meraki Group Policy L3 API Question

rodney2 — Wed, 04 Jun 2025 01:35:01 GMT

Yes, it is available when AD integration is enabled, just as @matt_uc mentioned. By the way, is this something that can also be done via the API?

Re: Meraki Group Policy L3 API Question

aleabrahao — Wed, 04 Jun 2025 09:42:47 GMT

Unfortunately not.

Re: Meraki Group Policy L3 API Question

rodney2 — Thu, 05 Jun 2025 04:40:17 GMT

Okay, thanks for the help!

Re: Meraki Group Policy L3 API Question

MilenaVens — Wed, 25 Feb 2026 12:48:18 GMT

@rodney2 wrote:
Hi everyone,

I’m working on a script that needs to add L3 firewall rules under a group policy, and I’m wondering if there’s any support for including a `source` field in the request payload. I couldn’t find any mention of this in the official documentation, but I’m curious if it’s supported unofficially or possibly planned for a future release.

According to for example, https://fast-pay.casinologin.mobi/ the schema for `L3FirewallRules` is as follows: and gain bonusses in cas

- `L3FirewallRules`: `object[]`
An ordered array of the L3 firewall rules
- `comment`: `string` — Description of the rule (optional)
- `destCidr*`: `string` — Destination IP address (IP, CIDR, FQDN, or 'any')
- `destPort`: `string` — Destination port (1–65535, range, or 'any')
- `policy*`: `string` — 'allow' or 'deny'
- `protocol*`: `string` — 'tcp', 'udp', 'icmp', 'icmp6', or 'any'

As you can see, there’s no mention of a `source` field. Has anyone tried including it anyway, or received clarification from the dev team?

Any insights would be greatly appreciated!

Thanks in advance!

Hey! I get what you're trying to do, and yeah, it’s a bit tricky when the documentation doesn’t cover something explicitly. If source isn’t listed in the schema for L3FirewallRules, it’s likely not officially supported. That said, some APIs do have undocumented or beta features, so it could be worth reaching out to the support team or checking for future release notes. If you're feeling adventurous, try testing with the field and see if the system accepts it. Fingers crossed it works!