Step 2 — SAGE connection

zrsPOS issues every document through your SAGE's API. You need:

• the API endpoint, including the port, for example https://sage.yourcompany.pt:5581;
• the API key (x-api-key) from your SAGE partner.

Enter both and press Save and test. Nothing is saved until SAGE has answered with its company name; the next steps unlock only after a successful test of the saved connection. The key is stored encrypted and never shown again; leave the field blank later to keep it.

Making your SAGE reachable

Your SAGE runs on your own network; zrsPOS runs in the cloud and must reach it over the internet, securely.

1. Publish the SAGE API on a fixed address (static IP or a DDNS name) with HTTPS.
2. On your firewall, allow only zrsPOS's address. We will give you the exact IP.
3. Keep the API key private. If it leaks, ask your SAGE partner for a new one and paste it here.

If the test fails

• Timeout / unreachable: the port is not forwarded, or the firewall blocks us. Check with your network provider.
• 401 / 403: the key is wrong or expired.
• Certificate error: the HTTPS certificate is self-signed or expired. Use a valid certificate.