Skip to content
DNSmigrator
betaDNS betaDNS hostingSetup guide checked 2026-09-27

Websupport

Websupport API key setup: generate an API key and secret in Websupport Admin; DNSMigrator uses the secret locally to sign each request.

On this page

Websupport API key permissions

Credential type
API key and API secret
Preview access
An API key and secret for a Websupport user with access to the domain.
Apply access
The same API key and secret used for preview; Websupport's published setup docs do not expose separate read-only and write scopes.
API endpoint
DNSMigrator uses the provider's fixed API endpoint.

Additional access

DNSMigrator first calls /v2/check, then reads the user's services and DNS records. Applying uses POST, PUT, and DELETE record endpoints. The API secret signs requests with HMAC-SHA1 and is never sent to Websupport.

DNSControl id

creds.json TYPE
{
  "TYPE": "WEBSUPPORT"
}

Create credentials

Generate an API key and secret in Websupport Admin; DNSMigrator uses the secret locally to sign each request.

Access you'll grant

Preview

An API key and secret for a Websupport user with access to the domain.

Apply

The same API key and secret used for preview; Websupport's published setup docs do not expose separate read-only and write scopes.

DNSMigrator first calls /v2/check, then reads the user's services and DNS records. Applying uses POST, PUT, and DELETE record endpoints. The API secret signs requests with HMAC-SHA1 and is never sent to Websupport.

Before you start

  • A Websupport user that owns or can manage the domains being connected.
  • Each DNS zone must already exist in Websupport Admin; the API cannot create or enumerate zones.

Setup steps

0 of 4 done

  1. Open the Security page

    Sign in to Websupport Admin and open Security. In the current account navigation, find API authentication under the security and login settings.

    Open Websupport Security

  2. Generate API credentials

    In API authentication, generate a new API key and API secret for this connection. Websupport's public API documentation does not list per-key scope controls, so the key follows the Websupport user's domain access.

  3. Copy the key and secret

    Copy both generated values before leaving the confirmation. Keep the pair together; DNSMigrator uses the API key as the Basic-auth username and derives a new request signature from the secret.

  4. Paste both values

    Paste the public identifier into API key and the paired secret into API secret. Do not calculate or paste an HMAC signature; DNSMigrator creates one for every request.

    API hostrest.websupport.sk

Troubleshooting

Websupport does not verify the credentials

Confirm the key and secret came from the same generated pair. Paste the raw secret, not a signature copied from an API example.

Authentication fails intermittently

Websupport signs requests with the current UTC timestamp. Correct the DNSMigrator host's system clock, then check access again.

The domain is not found

Add the domain in Websupport Admin first and ensure it belongs to the user that created the key. The API cannot list arbitrary zones or create a missing one.

Official documentation

Guide checked against the official documentation on .

Credential fields

FieldRequirementWhere to find it
API keyapiKeyRequiredThe API key generated in Websupport Admin → Security → API authentication.
API secretsecretRequiredThe API secret generated with the key. DNSMigrator keeps it as the HMAC-SHA1 signing secret; it is not sent in API requests.

Capabilities

Create zones
No
List zones
No
DNSSEC
Managed in the provider console
Minimum TTL
60 seconds
Apex CNAME
No
Read only
No

Record types

  • A
  • AAAA
  • CNAME
  • MX
  • TXT
  • SRV

Caveats

  • Only A, AAAA, CNAME, MX, TXT and SRV records can be managed; CAA values come back without flags and tag, so CAA records are not read, and NS and ANAME are left alone.
  • Websupport cannot list DNS zones through the API; enter the domain name, and add new domains in the Websupport admin first.
  • Null MX and SRV records without a target are rejected, and trailing spaces in TXT values are stripped.

Troubleshooting

Websupport does not verify the credentials
Confirm the key and secret came from the same generated pair. Paste the raw secret, not a signature copied from an API example.
Authentication fails intermittently
Websupport signs requests with the current UTC timestamp. Correct the DNSMigrator host's system clock, then check access again.
The domain is not found
Add the domain in Websupport Admin first and ensure it belongs to the user that created the key. The API cannot list arbitrary zones or create a missing one.

Related links

Websupport migration overviewMarketing overview and provider differences.Connect a providerHow connection checks and permissions work.Cloudflare → WebsupportRoute 53 → WebsupportAzure DNS → WebsupportCloud DNS → Websupport