Install and Configure the ATRS API
Install the API service, configure access and verify the connection from your application.
Install and start the ATRS API service, create credentials for your application and check that the application can reach it.
Before you begin
- Install the latest ATRS release on the Windows server that will run your reports.
- Have an administrator available to install the service and configure network access.
- Identify the Windows account the service will use and its access to the ATRS database, Tableau resources and output locations.
- Choose the protocol, hostname and port applications will use.
- Prepare a working Tableau report schedule and a test destination.
The service’s Windows account is separate from the ATRS user or API client used to authenticate API requests.
1. Install the API service
In the ATRS desktop application:
- Open Options → REST API.
- Under API Settings, click Install API.
- Enter the requested Windows credentials and click OK.
- Accept the installation confirmation with Yes, then dismiss the completion message with OK.
The ATRS API setup walkthrough shows the installation screens.
2. Configure the connection
With the API service stopped, review Protocol and Port in Options → REST API. Use a port that is available on this server.
| Setting | What to record |
|---|---|
| Protocol | http for a local connection check or https for the configured secure listener. |
| Hostname | The ATRS server name applications can reach. |
| Port | The port selected for this API installation. |
For HTTPS, complete Configure HTTPS for the ATRS API before starting the HTTPS listener. Selecting HTTPS also requires a certificate binding and client trust.
3. Start the API service
Click Start and confirm that the ATRS API Service shows as running. ATRS saves protocol and port settings when it starts the service.
Record the base address, such as http://localhost:9000 for a local check. Use the actual configured port. This example address does not discover your settings.
4. Create an API client
- Open Options → REST API → API Clients.
- Click Add and enter a name for the application.
- Click Save & Close.
- Store the generated client ID and secret securely.
Use these credentials for API-client authentication. Keep the secret out of shared collections and source control.
5. Test the connection locally
On the ATRS server, replace this address with its configured local address and call GET /api/Service/Ping:
$AtrsBaseUrl = "http://localhost:9000"
$AtrsPing = Invoke-RestMethod -Method Get -Uri "$AtrsBaseUrl/api/Service/Ping" -Headers @{Accept="application/json"} -TimeoutSec 30
if ($AtrsPing -ne 1) { throw "Unexpected Ping response" }Expect HTTP 200 and the JSON number 1. This confirms that the listener responds.
6. Test from your application host
Run the same check from the machine that will call ATRS, using the reachable server hostname. localhost on that machine refers to the application host.
If the local check succeeds but the remote check fails, check DNS, routing, the configured TCP port and firewall access. For HTTPS, also check the certificate hostname and trust chain.
7. Authenticate and verify a report
Follow Authentication and Token Management and complete its protected scheduler-state request. Either true or false confirms the protected request returned a scheduler-state value.
Then follow the Quick Start. Installation checks are complete when the application host can reach Ping, authenticate, read protected state and run the intended test schedule with verified output.
Troubleshooting
| Symptom | Next check |
|---|---|
| The service does not start | Service identity, configured port and Windows service diagnostics. |
| Ping fails locally | Running service, selected protocol and listener port. |
| Ping works locally only | Server hostname, firewall and network route. |
| HTTPS fails | Certificate binding, DNS name, expiry and client trust. |
| Protected requests fail | Token flow, bearer header and the caller’s permissions. |
Updated about 11 hours ago