Retrieve legal agreements and terms of service for GoDaddy products and services. This API provides programmatic access to agreement content, titles, and URLs for display in applications and compliance workflows. It supports multi-market localization with BCP-47 language codes, enabling region-specific legal text retrieval for international deployments.
1 endpointsThe GoDaddy Domains API (OTE - Operational Test Environment) provides programmatic access to domain-related actions including purchasing, renewing, managing nameservers, DNS records, and domain transfers. This is a test environment for development and integration testing before deploying to production. Updates to domains generally require the domain to be in an ACTIVE status, and some actions on protected domains require 2FA which is not supported via the API.
47 endpointsThe GoDaddy Orders API (OTE - Operational Test Environment) provides access to order history and billing information for products purchased through GoDaddy. This test environment allows developers to retrieve order details, track purchase history, and access invoicing information for domain registrations, renewals, hosting services, and other GoDaddy products before deploying to production.
2 endpointsThe GoDaddy Shoppers API (OTE - Operational Test Environment) provides programmatic access to customer account management, including creating subaccounts, managing shopper profiles, and accessing customer information. This test environment is designed for resellers and agencies managing multiple customer accounts before deploying to production. Shoppers are the core account entities in the GoDaddy system that own domains, orders, and other resources.
4 endpointsThe GoDaddy Subscriptions API (OTE - Operational Test Environment) provides programmatic access to recurring subscriptions and services including domains, hosting, SSL certificates, email services, and other GoDaddy products. This test environment allows developers to retrieve subscription details, manage renewals, check expiration dates, and access add-ons before deploying to production. Subscriptions represent ongoing services that require periodic renewal and payment.
3 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.