Getting started

Connection and security setup

Connection details and access control rules to review before calling the RDPLINE API.

Connection details

API calls must be sent to the domain https://api.rdpline.com. Calling the RDPLINE API server IP directly may fail certificate validation.

API address

https://api.rdpline.com

RDPLINE API server IP

125.141.143.200

Protocol / port

HTTPS / TCP 443

Access control

The RDPLINE API checks both API key authentication and whether the calling server IP is allowed. Both conditions must be met for a call to succeed.

Registering calling server IPs

The public IP of the server calling the API must be registered in advance. Requests from unregistered IPs are blocked regardless of whether the API key is valid.

  • Calling server IPs can be registered and reviewed under API key management after signing in to the portal.
  • If you call from multiple servers, register every public IP actually used for the calls.
  • Register the public IP used to reach the internet, not the server's private IP. When using NAT or a proxy, the external IP of that device is what must be registered.
  • Domain (DNS) names cannot be registered. Access control is evaluated against the IP at request time.
  • If an IP is going to change, register the new IP before the change. Once traffic comes from an unregistered IP, API calls are blocked immediately.

Customer firewall setup

In your firewall, you only need to allow outbound requests to the RDPLINE API.

Direction

Allowed target

Port

Outbound

125.141.143.200

TCP 443