getcname.php

[Wallvon]

Validate domain by CNAME

This endpoint allows you to add a domain using CNAME validation instead of DNS validation. It uses a POST request, which is confusing because it's called getcname but whatever.

Right now it is not possible to create an account with an domain that has been verified by CNAME via the API! Its only possible to manually add that in vPanel.
- BastelPichi

Required parameters:

• api_user
• api_key
  - username
• domain_name

XML API:

https://panel.myownfreehost.net/xml-api/getcname.php

Example response:

73081144a0525fde6ba1b0510684efcf

JSON API:

https://panel.myownfreehost.net/json-api/getcname.php

Example response:

73081144a0525fde6ba1b0510684efcf

---

Thanks to @BastelPichi for bringing up the missing endpoint.

[BastelPichi]

curl -X POST https://panel.myownfreehost.net/xml-api/getcname.php -d 'domain_name=domain.com&username=hname_12345678&api_user=XXXXXXXXX&api_key=XXXXXXXXXX' -u XXXXXXX:XXXXXXXXXX
Returns: 73081144a0525fde6ba1b0510684efcf

Using the json API vs the XML API makes no difference.
The username is irrelevant and doesnt matter. (they probably left it in by mistake), however its still good practice to send the actual username.

By creating an CNAME record from HASH_VALUE.domain.com to ns1.byet.org the domain can be added to cPanel without changing nameservers.

Right now it is not possible to create an account with an domain that has been verified by CNAME via the API! Its only possible to manually add that in vPanel.

[BastelPichi]

You shouldn't need the username now anymore.

[Wallvon]

You shouldn't need the username now anymore.

Seems like they've broken the endpoint with that change since now I only get ERROR :The API key or API username entered is not valid. .

It also seems like they changed back to query parameters instead of multipart form, just like all other endpoints.

[BastelPichi]

You shouldn't need the username now anymore.

Seems like they've broken the endpoint with that change since now I only get ERROR :The API key or API username entered is not valid. .

It also seems like they changed back to query parameters instead of multipart form, just like all other endpoints.

The other endpoints do use body data (at least thats how your docs specify it and that way it also works). What happens if you use body data?

[Wallvon]

The other endpoints do use body data (at least thats how your docs specify it and that way it also works). What happens if you use body data?

I get the same error then it seems.

[BastelPichi]

The other endpoints do use body data (at least thats how your docs specify it and that way it also works). What happens if you use body data?

I get the same error then it seems.

Thats interesting, ill look into this later.

[Wallvon]

I've contacted iFastNet about this and I'm currently waiting for a reply ^

[Wallvon]

This issue is resolved now.