Hostinger API token setup
A short walkthrough for producing the credential AgentSOC needs to power Hostinger VPS instances on and off.
Screenshots: image placeholders below point at
docs/images/hostinger-*.png. Capture each screenshot and drop it in at that path — the captions describe exactly what to show.
How the connection works
AgentSOC authenticates to Hostinger with a single API token generated in hPanel. One value goes into the credential form:
| Value | What it is |
|---|---|
| API Token | A bearer token for the Hostinger VPS API |
Scope of support: the Hostinger integration can only power VPS instances on and off. IP blocking and instance isolation are not available on Hostinger's VPS API.
Step 1 — Open the Hostinger API settings
Sign in to hPanel and open Account → API (under the Developers section).

Step 2 — Generate an API token
- Click Generate token (or Create token).
- Give it a recognizable name, e.g.
agentsoc-soar. - Copy the generated token.
The token is shown only once. Copy it now — if you lose it, generate a new one and delete the old token. Store it like a password.

Step 3 — Add the credential in AgentSOC and validate
- In AgentSOC, open AgentSOAR → Settings → Credentials (
/agentsoar/settings/credentials). - Add a Hostinger credential and paste the API Token from Step 2.
- Save. AgentSOC validates the token by listing your VPS instances.
- Once it shows Healthy, the Hostinger power action is ready to use.

Troubleshooting
| Error | Likely cause and fix |
|---|---|
Hostinger API returned 401 | The API token is wrong, was mistyped, or has been revoked. Generate a fresh token (Step 2). |
Hostinger API returned 403 | The token lacks access to the VPS API, or the account has no VPS plan. |
| Network error | hPanel or the Hostinger API is temporarily unreachable. Retry validation shortly. |
Reference: Hostinger — Generating an API token