CAA Record Parser API

Overview

To use CAA Record Parser, you need an API key. You can get one by creating a free account and visiting your dashboard.

POST Endpoint

https://api.apiverve.com/v1/caaparser

Example

How to call the CAA Record Parser API in different programming languages.

curl -X POST \
  "https://api.apiverve.com/v1/caaparser" \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\""
}'

const response = await fetch('https://api.apiverve.com/v1/caaparser', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\""
})
});

const data = await response.json();
console.log(data);

import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

payload = {
    "record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\""
}

response = requests.post('https://api.apiverve.com/v1/caaparser', headers=headers, json=payload)

data = response.json()
print(data)

package main

import (
    "fmt"
    "io"
    "net/http"
    "bytes"
    "encoding/json"
)

func main() {
    payload := map[string]interface{}{
        "record": "example.com. 3600 IN CAA 0 issue "letsencrypt.org""
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/caaparser", bytes.NewBuffer(jsonPayload))

    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

{
  "status": "ok",
  "error": null,
  "data": {
    "raw_record": "example.com. 3600 IN CAA 0 issue \"letsencrypt.org\"",
    "parsed": {
      "domain": "example.com",
      "ttl": 3600,
      "class": "IN",
      "flags": 0,
      "tag": "issue",
      "value": "letsencrypt.org"
    },
    "ca_info": {
      "name": "Let's Encrypt",
      "type": "Free",
      "wildcard_support": true
    },
    "interpretation": {
      "meaning": "Only letsencrypt.org is authorized to issue certificates",
      "restriction": "Restricted to specific CA",
      "critical": false,
      "critical_explanation": "Non-critical - CA may proceed if not understood"
    },
    "tag_description": "Authorizes a CA to issue certificates (any type)",
    "is_valid": true
  }
}

Authentication

The CAA Record Parser API requires authentication via API key. Include your API key in the request header:

X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the CAA Record Parser API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the CAA Record Parser API:

Response

The CAA Record Parser API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.

Other Response Formats

<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <raw_record>example.com. 3600 IN CAA 0 issue &quot;letsencrypt.org&quot;</raw_record>
    <parsed>
      <domain>example.com</domain>
      <ttl>3600</ttl>
      <class>IN</class>
      <flags>0</flags>
      <tag>issue</tag>
      <value>letsencrypt.org</value>
    </parsed>
    <ca_info>
      <name>Let&apos;s Encrypt</name>
      <type>Free</type>
      <wildcard_support>true</wildcard_support>
    </ca_info>
    <interpretation>
      <meaning>Only letsencrypt.org is authorized to issue certificates</meaning>
      <restriction>Restricted to specific CA</restriction>
      <critical>false</critical>
      <critical_explanation>Non-critical - CA may proceed if not understood</critical_explanation>
    </interpretation>
    <tag_description>Authorizes a CA to issue certificates (any type)</tag_description>
    <is_valid>true</is_valid>
  </data>
</response>

status: ok
error: null
data:
  raw_record: example.com. 3600 IN CAA 0 issue "letsencrypt.org"
  parsed:
    domain: example.com
    ttl: 3600
    class: IN
    flags: 0
    tag: issue
    value: letsencrypt.org
  ca_info:
    name: Let's Encrypt
    type: Free
    wildcard_support: true
  interpretation:
    meaning: Only letsencrypt.org is authorized to issue certificates
    restriction: Restricted to specific CA
    critical: false
    critical_explanation: Non-critical - CA may proceed if not understood
  tag_description: Authorizes a CA to issue certificates (any type)
  is_valid: true

Response Structure

All API responses follow a consistent structure with the following fields:

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

Headers

Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →

GraphQL AccessALPHA

Access CAA Record Parser through GraphQL to combine it with other API calls in a single request. Query only the caa record parser data you need with precise field selection, and orchestrate complex data fetching workflows.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

POST https://api.apiverve.com/v1/graphql

query {
  caaparser(
    input: {
      record: "example.com. 3600 IN CAA 0 issue "letsencrypt.org""
    }
  ) {
    raw_record
    parsed {
      domain
      ttl
      class
      flags
      tag
      value
    }
    ca_info {
      name
      type
      wildcard_support
    }
    interpretation {
      meaning
      restriction
      critical
      critical_explanation
    }
    tag_description
    is_valid
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The CAA Record Parser API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →

Rate Limiting

CAA Record Parser requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →

Error Codes

The CAA Record Parser API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →

SDKs for CAA Record Parser

Official CAA Record Parser packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

JitPack

No-Code Integrations

CAA Record Parser works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Zapier

Make

Pipedream

n8n

Power Automate

Frequently Asked Questions

People who used this also used...

Based on your interest in CAA Record Parser, you might also like these APIs:

SRV Record Parser

SRV Record Parser analyzes DNS SRV records and extracts service location information including priority, weight, port, and target server details.

1 credit per call

Shoe Size Converter

Shoe Size Converter is a tool for converting shoe sizes between US, UK, EU, CM, JP, AU, MX, and KR standards. It supports men, women, unisex, and child sizes.

1 credit per call

Ring Size Converter

Ring Size Converter is a tool for converting ring sizes between US, UK, EU, JP, CH, and AU standards. It can also convert from diameter measurements in millimeters.

1 credit per call