Skip to content

API reference

Delete DNS record

domains.DeleteDnsRecordWriteAPI key

Delete a DNS record set from a hosted domain. Records required for Brigg hosting and certificate validation cannot be deleted.

POST/v1/operations/domains.DeleteDnsRecord
On this page

Access & visibility

Allow domains.DeleteDnsRecord on your API key.

Workspace access by default. Private member data requires approved member delegation through Brigg-Act-As; the key supplies permissions while private ownership and project boundaries remain enforced.

Set up authentication · Choose permissions

Request fields

Send a JSON object with the following fields. Required fields must be included; omit optional fields you do not need.

idstringRequired

Use the hosted domain's id. Read ListDnsRecords before choosing the exact name and type to delete. domains.ListHostedDomains.

At least 1 character. At most 80 characters.

namestringRequired

Record name relative to the domain: '@' for the domain itself, 'www', 'mail', '_dmarc', 'selector._domainkey'.

At most 253 characters.

typestringRequired

One of A, AAAA, CNAME, MX, TXT. The apex NS/SOA are Brigg's own and refused reserved.

At most 8 characters.

Change a hosted DNS record set

Select the domain's id from List hosted domains. The domain must be active and DNS-hosted by Brigg. A website hostname or app ID is not a hosted-domain ID.

Set replaces every value for one name/type pair. Read the current set first and include values you want to retain. Delete removes that whole set. Use @ for the apex, www for a subdomain, and bare TXT text without surrounding quotes. MX values contain a numeric priority followed by the mail hostname. TTL is in seconds.

A successful response confirms the stored change, not global DNS propagation; caches can retain the old value until its TTL expires. Brigg-managed website aliases, certificate records and zone records are protected. A CNAME cannot coexist with another record type at the same name. Use the website connection operations to manage Brigg-hosted sites.

Response

Returns 200 OK with a JSON body.

okbooleanRequired

Whether the action completed successfully.

Errors & retries

Set BRIGG_REQUEST_ID once for each logical action. The samples send it as Idempotency-Key. Reuse the same value and body on retries, including after a timeout; a missing response does not prove the action failed.

For rate limits, follow the server’s retry guidance and back off. See HTTP errors and safe retries and limits.

HTTP status Code What to do
400 invalid_json Send a JSON object with Content-Type: application/json.
400 invalid_input Check the request fields and types. Supply a stable Idempotency-Key containing 1–200 characters.
401 invalid_key The workspace API key is missing, invalid or revoked.
403 forbidden Check the key’s operation and resource grants. If Brigg-Act-As is supplied, the key must be authorized to delegate to that member.
404 not_found The requested operation or resource is not available to this credential.
429 rate_limited Wait for Retry-After before retrying. Reuse the original Idempotency-Key.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "Use the hosted domain's id. Read ListDnsRecords before choosing the exact name and type to delete. [domains.ListHostedDomains](/reference/domains/ListHostedDomains)."
    },
    "name": {
      "type": "string",
      "maxLength": 253,
      "description": "Record name relative to the domain: '@' for the domain itself, 'www', 'mail', '_dmarc', 'selector._domainkey'."
    },
    "type": {
      "type": "string",
      "maxLength": 8,
      "description": "One of A, AAAA, CNAME, MX, TXT. The apex NS/SOA are Brigg's own and refused `reserved`."
    }
  },
  "required": [
    "id",
    "name",
    "type"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "id": "e_example",
      "name": "www",
      "type": "CNAME"
    }
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean",
      "description": "Whether the action completed successfully."
    }
  },
  "required": [
    "ok"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "ok": true
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.