SolumeCore API Overview: REST, Webhooks, MCP and Bots

SolumeCore gives you several ways to automate your services and to be told what is happening, and each one fits a different job. The REST API with an API key controls your VPS and VDS from code. Webhooks and integrations push events from SolumeCore to your own systems, Discord, Slack, Telegram, Teams or email. The AI API (MCP) lets an assistant such as Claude or ChatGPT manage your servers under your rules. The Discord bot lets your community check status and wake a server. This page is the map: what each surface does, how it authenticates and where to read more.

All of them are available from the client panel (dashboard.solumecore.com) under the Account menu, and all of them are tied to your own account: they can only see and act on the services that belong to you.

Which one should I use?

How they compare

Quick start with the REST API

The base address is https://api.solumecore.com, and every endpoint starts with /v1. Create a key, ask support to authorize the public IP your code runs from (see API keys), then:

export SOLUME_API_KEY="sk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

# List services
curl https://api.solumecore.com/v1/services \
  -H "Authorization: Bearer $SOLUME_API_KEY"

# Restart one (answers 204 with no body)
curl -X POST https://api.solumecore.com/v1/services/vps-1000/power/restart \
  -H "Authorization: Bearer $SOLUME_API_KEY"

Responses are JSON with Spanish keys and values. A service looks like this:

{
  "id": "vps-1000",
  "hostname": "web-prod",
  "estado": "ACTIVO",
  "plan": "VPS 4 GB",
  "ip": "203.0.113.42"
}

estado is one of APROVISIONANDO, ACTIVO, SUSPENDIDO, PAUSADO, CANCELADO or ERROR. GET /v1/services/:id adds fechaProximaRenovacion.

Details worth knowing about the Client API

The Client API reference lists the endpoints. These points from how the API behaves today complete it:

• Paths: with the base address above, the endpoint for one service is https://api.solumecore.com/v1/services/vps-1000. Do not add /v1 twice.
• What gets listed: GET /v1/services returns every service on your account, whatever its type. Power and firewall actions are designed for VPS and VDS services; on other kinds of service you will typically get a 409.
• Errors: JSON { "error": "..." }, with the message in Spanish for now. Rely on the status code: 400 invalid input, 401 missing or bad key, 403 IP not authorized, account suspended or closed, or IP blocked, 404 the service does not exist or is not yours, 409 the service is not active, is under maintenance, has no IP yet or is blocked by usage or security rules when starting, 429 rate limit (read retry-after), 502 or 503 the node or the firewall did not answer, so retry later.
• Power: POST /v1/services/:id/power/start, stop or restart, answered with 204.
• Reading the firewall returns the address and these lists:

{
  "ip": "203.0.113.42",
  "geoblock": ["CN"],
  "geoPolicy": "blacklist",
  "srcwl": ["198.51.100.0/24"],
  "asnBlock": ["4837"],
  "blacklist": [{ "ip": "192.0.2.9", "manual": true }]
}

• Changing the firewall with POST or DELETE on /v1/services/:id/firewall/:feature answers { "ok": true }. The DELETE request carries the same JSON body as the POST. Besides the rules in the reference, two more exist: geo-rate (country, proto as tcp or udp, and pps; remove it with country and proto) and fivem-cache (empty body {}).
• Settings, not entries: rdp-filter, ssh-filter, udp-strict, geoblock-policy and filter-mode are switched by sending a new value with POST. A DELETE on them returns 400.
• Rate limits are counted per key, per source IP and per group (reading, power, firewall). The defaults are 300, 20 and 60 requests per minute, and SolumeCore can change them per key.

Conventions shared by every surface

• Everything is HTTPS. Secrets (API keys, whsec_ webhook secrets, slm_ai_ tokens, destination URLs) are shown once or stored encrypted, and you can revoke or rotate them.
• Creating a long-lived credential asks you to confirm it is you, and it cannot be done from a support session. You are notified when one is created.
• Event and field names in webhook payloads are Spanish and stable. AI tool names and MCP errors are English.
• Nothing here changes your plan, your prices or your billing: those are managed in the panel. See Account security for how to protect the credentials.

Related documents

• Client API reference
• Account API keys
• Webhooks and account events
• Integrations and notifications
• AI and MCP API
• Client panel tour

FAQ

Does SolumeCore have a public API?

Yes. The REST API at https://api.solumecore.com/v1 lets you list your services, control power and manage the firewall of VPS and VDS services with an API key. Webhooks, integrations and an MCP server for AI assistants cover the other directions.

Can I order or cancel services with the API?

Not with the REST API: it covers listing, power and firewall. Ordering, billing and cancellations are done in the client panel.

Which is better for notifications: webhooks or integrations?

Use an integration if you want Discord, Slack, Telegram, Teams or email, filters and your own message text. Use a webhook if you only need a simple signed POST to your server. An HTTP integration gives you a signed POST with filters too.

Is there an SDK?

No SDK is documented. The REST API is plain HTTP and JSON, so any HTTP client works; the examples in these guides use curl, Node.js and Python.

Where can I get help with an integration?

Open a ticket from the panel or visit the help center. For API keys, include the key name and never paste the secret.