---
name: Testing the SkillGuard api-server from the shell
description: How to reach the api-server with curl during development (external proxy fails).
---

# Testing the api-server from the shell

Curling the api-server through the external proxy (`$REPLIT_DEV_DOMAIN/api/...`)
fails during development — it returns HTTP 000 / connection refused (the proxy
routes by the selected artifact + mTLS, so a bare curl does not reach it).

**How to apply:** curl the api-server directly on its local port instead, e.g.
`http://localhost:8080/api/scans`. Confirm the port from the api-server workflow
log line `Server listening port: <PORT>` (it reads `PORT`, defaulting to 8080).
The web artifact's preview, however, reaches the API fine through the proxy.