Having different z/OS Connect APIs on different endpoints would not help anything since what you are saying is that there is not direct way to control API usage (in z/OS Connect) based on the request origin. So, moving the z/OS Connect API to another endpoint (another z/OS Connect server) does not solve the problem, because that server cannot control the Request origin either.
Also an IDEA has been opened on August 4th ZCEE-I-582
------------------------------
Scott Adams
------------------------------
Original Message:
Sent: 08/14/26 05:18 AM
From: Samantha Catling
Subject: zOS Connect Defining Filters (Url / IP Address) that can access native server
Hi Scott, thank you for the question.
I've spoken to the team and they've explained there isn't a direct way to filter out APIs based on request origin - it's a blanket all or nothing using tcpoptions on the endpoints. You could have individual APIs on different endpoints. I believe the team have spoken to you with more details, but if you haven't already done so, please raise an Idea.
------------------------------
Samantha Catling
UX & Visual Designer, Z Integration
IBM
------------------------------