Here’s a technical blog post based on the On-Premise Setup guide from the SQL Account API documentation that you shared:

---

How to Set Up the SQL Account API On-Premise: A Practical Guide

Integrating your accounting system with external applications via APIs can unlock powerful automation and connectivity. If you’re using SQL Account and want to expose its RESTful API from your own server environment (not in the cloud), this on-premise setup guide walks you through the end-to-end process.

---

🧩 What Is On-Premise API Hosting?

Most cloud services host APIs for you, but on-premise API setup means hosting the API service within your own network or office infrastructure. You retain full control of the environment, data storage, and networking — ideal for organisations with strict data governance or compliance needs.

In the context of SQL Account API, on-premise setup enables your accounting system to act as an API server that external systems can connect to securely over the internet.

---

✅ Prerequisites — What You’ll Need

Before installing the SQL Account API service on-premise, make sure your environment meets these requirements:

🖥️ System Requirements

• Operating System: Windows 11 or later (64-bit recommended)
• CPU: Intel i5 / i7 or higher
• RAM: Minimum 8 GB (12 GB+ recommended)
• SQL Account Version: 5.2025.1038.875 or later
• Firebird Database: Version 3.0.9 or above
• Fixed Internal IP: Either a DHCP reservation or static IP
• Public IP Address: Dedicated public IP for external accessibility (see below)

---

🌐 Why You Need a Public IP Address

To allow external systems (e.g., mobile apps or third-party integrations) to reach your API endpoint, you must expose your service over the internet securely.

• Use tools like SQL Connect Detector to verify your public IP is active.
• If your ISP hasn’t provided a public IP, request a dedicated one.
• Your router must be configured appropriately with port forwarding (explained next).

---

🛠 Step-By-Step On-Premise Setup

1. Install the SQL API Service

1. Open the SQL Account application.
2. From the Logon Screen, click the ⚙️ Settings icon.
3. Right-click on your company database.
4. Select “Configure API Service…”.
5. Click Install to deploy the service.
   This process registers the API component on your server environment.

---

2. Start the API Service

After installation:

• Start the service from within the SQL Account interface.
• When the service is running, the status indicator will show Service is running.
  This confirms the API is active locally.

---

3. Configure Port Forwarding

This is a critical step to allow external connectivity.

1. In SQL Account, click Show Tips to see your port forwarding details (internal and external settings).
2. Access your router’s admin interface using the gateway IP shown.
3. Navigate to Port Forwarding, Virtual Server, or similar section.
4. Create a new rule with the following settings:

Setting	Value	Description
Service Name	SQL Account API Service	Friendly identifier
Protocol	TCP	Protocol used
External/Public Port	443	Port exposed to the internet
Internal/Private Port	443	Port listening internally
Internal IP Address	192.168.x.x	IP of your SQL server

5. Save and apply the rule.

---

4. Verify the Connection

Once the port forwarding rule is active:

• Back in SQL Account, use the Test Connection button to validate external reachability.
• A ✅ OK status means everything is configured correctly and the API can receive external requests.

---

🔐 Security Considerations

Exposing internal services to the internet requires careful attention:

• HTTPS: Use SSL/TLS certificates so communication is encrypted.
• Firewalls: Only allow traffic on required ports (e.g., port 443).
• Rate Limiting & API Keys: If possible, restrict API access to trusted clients.
• Monitoring: Use logging tools to audit access and detect anomalies.

Note: The documentation does not cover SSL setup — you may need to configure this at the server or reverse proxy level.

---

📌 Summary

Configuring the SQL Account API on-premise gives you control over your data and integration endpoints. The setup involves:

1. Meeting minimum system requirements.
2. Installing and starting the API service.
3. Configuring public IP and port forwarding.
4. Verifying connectivity.

Once done, your SQL Account instance can act as a robust API provider for mobile apps, BI tools, or custom integrations.

---

If you’d like, I can also write a follow-up blog on securing the API behind HTTPS or connecting client applications to it!