Agent pattern or Agent architecture.
We want access to functionality or data offered by and application or database, but the application/database does not offer the endpoints we want and we do not want to modify the existing application/database.
Incoming traffic is not possible or unwanted due to firewalls and routing policies.
Implement a standalone application, an agent, with integrates with the application or database you want to extend with new integration functionality. The agent will act as a communication proxy between the target application/database and the outside world.
The agent will initiate all communication, and all communication is HTTPS based. Firewalls must allow outgoing HTTPS traffic (port 443), but can block all incoming traffic.
This pattern was (to my knowledge) first described by Thor Henning Hetland June 2015.