DNS

Now that the website is created, we can use tagId from the first step to get DNS records.

DNS records are a key concept in the EdgeTag system. The entire infrastructure is deployed as a first-party ecosystem, enabling better security, privacy, and signal collection. But to be a first-party, they will need to add DNS records returned from the API to their name server hosting provider.

Our system has two DNS records: TXT and CNAME.

TXT is used to verify domain ownership, and CNAME is used to route traffic to a dedicated endpoint in Cloudflare.

GET /tag/verify/mapping/{tagId}

JavaScript

fetch('https://api-sandbox.edgetag.io/tag/verify/mapping/{tagId}', {
  method: 'GET',
  headers: {
    'Accept': 'application/json',
    'Authorization': 'Bearer your-token',
    'Team-Id': '{your-team-id}'
  }
})

cURL

curl --request GET \
  --url https://api-sandbox.edgetag.io/tag/verify/mapping/{tagId} \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer {your-token}' \
  --header 'Team-Id: {your-team-id}'

If you receive true for propertyvalid in the response, that means DNS records are set up correctly, and you are good to go.

If you call this endpoint multiple times and the TXT record, for example, is already mapped, you will only see CNAME in the response, as that is the only record left to set.