Authenticate to the Splynx ISP billing API using API keys or HMAC signatures
domain: splynx.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an API key in Splynx under Administration -> API keys, choosing either Unsecure access (basic) or signature-based access, and set the key's per-module permission scopes.
For Basic auth mode, Base64-encode the key/secret pair and send it as Authorization: Basic <base64>.
For signature (HMAC) mode, send Authorization: Splynx-EA (key=<KEY>&nonce=<nonce>&signature=<signature>), where signature is an uppercase HMAC-SHA256 of nonce+key using the secret, and nonce is an incrementing integer counter rather than a wall-clock timestamp.
Send all requests to https://<your-splynx-url>/api/2.0/ using standard HTTP verbs, remembering that updates require PUT rather than PATCH.
For filtered searches, build main_attributes/additional_attributes objects with operators like =, !=, BETWEEN, LIKE, IN, REGEXP and encode them onto the URL as a query string rather than passing simple flat query params.
Known gotchas
Splynx's own docs flag PUT-for-update as a common mistake — sending PATCH or POST for an update will not behave as expected.
API keys are scoped per module (Administration -> API keys -> Permissions) — a key can silently be denied access to a specific module rather than returning an obvious auth error.
There is no built-in API rate limiting as of current docs, so nothing will throttle a runaway integration — pace your own requests.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?