GET /health
Check that the RemakeCV API is reachable. The only endpoint requiring no authentication, which makes it the right first step when debugging an integration.
GET /health returns {"status":"ok"} and requires no authentication, because it sits ahead of the RemakeCV API's auth layer. Use it to verify network connectivity and that the service is reachable, separately from any question about whether your API key is valid or your company has the API enabled.
Request
curl https://app.remakecv.com/api/public/v1/healthNo headers required.
Response
{ "status": "ok" }This endpoint returns a bare object rather than the standard data/pagination/error envelope, because it sits ahead of the authenticated API layer.
Why it is useful
Because it separates two failure modes that otherwise look identical from the client side:
/health | An authenticated call | Diagnosis |
|---|---|---|
| Succeeds | Fails 401 | Your key is wrong, expired or revoked |
| Succeeds | Fails 403 api_disabled | The API is not enabled for your company |
| Fails | Fails | Network, DNS or the service is down |
Start every integration debug here.
Where to go next
Once /health responds, move on to authentication and then GET /templates, which is the simplest authenticated call to confirm a key works.
Should I poll it?
For an uptime check, a low-frequency poll is reasonable. Do not use it as a keepalive before every request — it adds a round trip without telling you anything about whether the next call will succeed.
Frequently asked questions
- Does /health need an API key?
- No. It sits ahead of the authentication middleware, which is what makes it useful for isolating connectivity problems from credential problems.
- Does it count against my rate limit?
- No. Rate limiting is applied after authentication, and /health runs before it.
Related articles
Last updated . Still stuck? Email support@remakecv.com or book a call.