.se and .nu domain operations

.se and .nu domains are managed by Internetstiftelsen, the Swedish Internet Foundation. Both TLDs run on the same registry platform and follow the same rules, and each has its own endpoint for generating auth codes at the registry.

Request an auth code

.se and .nu auth codes are owned by the registry. A registrar cannot choose the value: the registry generates it and returns it when the domain is registered, and it is not exposed in a later domain info request. This endpoint requests a fresh code from the registry and stores it, which is how a code consumed by a transfer is replaced.

curl "$OPUSDNS_API_BASE/v1/domains/tld-specific/se/example.se/auth_code/request" \
  --request POST \
  --header "X-Api-Key: $OPUSDNS_API_KEY"

.nu has its own path, and each endpoint accepts only names within its own TLD:

curl "$OPUSDNS_API_BASE/v1/domains/tld-specific/nu/example.nu/auth_code/request" \
  --request POST \
  --header "X-Api-Key: $OPUSDNS_API_KEY"

Response

{
  "name": "example.se",
  "success": true,
  "auth_code": "TEST-260908-OPUSDN-7d146e3b-f6df-4302-ad95-cf28574e4354"
}

Note: Unlike registries that email the code to the registrant, this endpoint returns it directly. Requesting a new code invalidates the previous one, so only call it when the current code is unusable.

Prerequisites

The domain must be sponsored by your account. The endpoint requires the same permission as a domain update.

Transfer behavior

.se and .nu transfers are immediate. There is no pending period, no approval and no rejection: a transfer request either completes at once or fails.

This has two consequences worth planning for:

• the gaining registrar learns the outcome from the transfer response itself, with no notification to wait for;
• the losing registrar is notified after the fact and cannot prevent the transfer.

Transfers do not extend the registration period, and the auth code is consumed in the process. Request a new one through the endpoint above if the domain needs to be transferable again.

Registrant verification

Internetstiftelsen may hold a new registration while it verifies the registrant's data. The domain is created, but the registry applies serverHold, serverTransferProhibited and serverRenewProhibited until the check clears, so it does not resolve and cannot be transferred or renewed in the meantime.

The check clears when the registry accepts the registrant data, or when the registrant is replaced with one that passes. In either case the registry reports the outcome and the statuses are reconciled onto the domain automatically.

Contact attributes

Every registrant needs REGISTRY_SE_ORG_NO, a personal or organization number prefixed with a bracketed country code. See .se or .nu in the TLD Knowledge Base for the format and its validation rules.

Related API Reference

• POST /v1/domains/tld-specific/se/{domain_reference}/auth_code/request
• POST /v1/domains/tld-specific/nu/{domain_reference}/auth_code/request