The GoDaddy Abuse API (OTE - Operational Test Environment) is the abuse reporting interface for properties hosted with GoDaddy. It lets reporters file structured abuse tickets covering phishing, malware, child sexual abuse material, network abuse, copyright, and spam, and it lets ticket creators retrieve the status of cases they have opened. With six endpoints across v1 and v2, the API is purpose-built for high-signal abuse intake from registries, CERTs, and security platforms.
6 endpointsManage SSL/TLS certificates through GoDaddy's certificate authority infrastructure. Order, validate, issue, reissue, renew, and revoke SSL certificates with support for domain validation workflows, callback webhooks, and email-based verification. The API handles the complete certificate lifecycle including CSR validation, CA approval workflows, and certificate bundle download.
25 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fote-godaddy.com" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fote-godaddy.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.