hermes-skills/skills/devops/server-architecture-plan/references/netcup-api-investigation.md

netcup API Access Investigation — Jul 8, 2026

Summary

The netcup REST API was NOT successfully configured. All three API paths returned errors or authentication failures.

Endpoints Tested

SCP REST API (servercontrolpanel.de)

• Endpoint: https://www.servercontrolpanel.de/scp-ui/api/v1/servers
• Auth tried: X-API-Key header, Authorization: Bearer header
• Result: HTTP 200 — returns SCP login HTML, not JSON
• Body contains: <nc-unauthorized></nc-unauthorized> — CCP API key doesn't authenticate SCP Keycloak
• SCP version: 2026.0703.095128

CCP REST API (customercontrolpanel.de)

• Endpoint: /rest/v1/servers, /api/v1/servers
• Auth tried: X-API-Key, Bearer, query param
• Result: HTTP 404 — all paths

JSON-RPC (ccp.netcup.net)

• Endpoint: https://ccp.netcup.net/run/webservice/servers/endpoint.php?JSON
• Auth: {"action":"getProducts","param":{"apikey":"..."}}
• Result: 200, but "Invalid entry for field apikey" — needs customer# + API password

Endpoint	HTTP	Auth	Result
ccp.netcup.net/webservice/v2_0/	404	SOAP	Not Found
ccp.netcup.net/endpoint.php?JSON	200	JSON-RPC	"Invalid apikey"
customercontrolpanel.de/rest/v1/servers	404	X-API-Key	Not Found
servercontrolpanel.de/scp-ui/api/v1/servers	200	X-API-Key	Returns login page
servercontrolpanel.de/scp-ui/api/v1/openapi	200	X-API-Key	Same — HTML, not JSON

Likely Fix

SCP needs its own API key generated within the SCP interface (not CCP Master Data). Or JSON-RPC with customer number + API password.

Status

netcup API: UNCONFIGURED. Provisioning via web interface + SSH only.