GoDaddy Shoppers API (OTE)

Name: GoDaddy Shoppers API (OTE) API
Brand: GoDaddy Shoppers API (OTE)
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsCustomer Managementapikey4 EndpointsREST

For Agents

Manage GoDaddy customer accounts and shopper profiles: create subaccounts, retrieve shopper information, and manage customer relationships in the OTE test environment.

Connect the GoDaddy Shoppers API (OTE) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GoDaddy Shoppers API (OTE), or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with GoDaddy Shoppers API (OTE) API.

Create subaccounts under a reseller or parent account

Retrieve shopper profile information including contact details and account status

Manage customer account relationships for resellers and agencies

Access shopper IDs for use with other GoDaddy API operations

GET STARTED

Start building with GoDaddy Shoppers API (OTE) API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use GoDaddy Shoppers API (OTE) API for, with concrete tasks.

★ Reseller Account Provisioning

Web hosting resellers and agencies can programmatically create and manage customer subaccounts. POST /v1/shoppers/subaccount creates a new shopper account linked to the reseller, returning a shopper ID that can be used with the X-Shopper-Id header in Domains and Orders API calls. This enables white-label domain management where customers never interact directly with GoDaddy.

POST /v1/shoppers/subaccount with customer contact details to create the account, then use the returned shopperId with X-Shopper-Id header in domain operations.

Multi-Tenant Customer Management

SaaS platforms offering domain services can maintain separate shopper accounts per customer for billing isolation and access control. GET /v1/shoppers/{shopperId} retrieves profile information, and PUT /v1/shoppers/{shopperId} updates account details. Combined with the Domains and Orders APIs, this enables full multi-tenant domain portfolio management.

GET /v1/shoppers/{shopperId} to retrieve customer profile, then use that shopper ID in GET /v1/domains with X-Shopper-Id to list their domains.

Agency Customer Onboarding

Web agencies onboarding new clients can automate account creation and initial domain setup. POST /v1/shoppers/subaccount provisions the account, followed by POST /v1/domains/purchase with the X-Shopper-Id header to register domains under the client's account. Agents can orchestrate multi-step onboarding workflows without manual account creation.

POST /v1/shoppers/subaccount for the new client, capture the shopperId, then POST /v1/domains/purchase with X-Shopper-Id header to register their domain.

AI Agent for Customer Operations

Let an AI agent handle customer account tasks for a reseller — creating subaccounts, looking up shopper information, and managing customer relationships. Through Jentic, the agent loads only the required operations and the GoDaddy API key is injected at execution time.

Use the Jentic search query 'create godaddy subaccount' to find POST /v1/shoppers/subaccount, load its schema, and execute with customer contact information.

Key Endpoints

4 endpoints — the godaddy shoppers api (ote - operational test environment) provides programmatic access to customer account management, including creating subaccounts, managing shopper profiles, and accessing customer information.

METHOD

PATH

DESCRIPTION

POST

/v1/shoppers/subaccount

Create a new subaccount under the authenticated reseller account

GET

/v1/shoppers/{shopperId}

Retrieve shopper profile information

PUT

/v1/shoppers/{shopperId}

Update shopper profile information

GET

/v1/shoppers

List shoppers with filtering options

POST

/v1/shoppers/subaccount

Create a new subaccount under the authenticated reseller account

GET

/v1/shoppers/{shopperId}

Retrieve shopper profile information

PUT

/v1/shoppers/{shopperId}

Update shopper profile information

GET

/v1/shoppers

List shoppers with filtering options

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

GoDaddy API keys are stored encrypted in the Jentic vault and injected as the Authorization header at execution time. Raw keys never appear in agent prompts or transcripts.

Intent-based discovery

Agents search by intent such as 'create subaccount' or 'get shopper info' and Jentic returns the matching endpoint with its schema.

Time to first call

Direct GoDaddy integration: 1 day to model shoppers and subaccounts. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

GoDaddy Domains API (OTE)

Manages domains owned by shoppers created via the Shoppers API.

Use Shoppers API to create customer accounts, then use Domains API with X-Shopper-Id to manage domains for those customers.

Complementary

GoDaddy Orders API (OTE)

Retrieves order history for shoppers managed via the Shoppers API.

Use Shoppers API to manage customer accounts and Orders API to track their purchase history.

Alternative

Auth0 Management API

Alternative customer identity and account management for custom applications.

Use Auth0 for application user management; use GoDaddy Shoppers API for domain service customer account management.

FAQs

Specific to using GoDaddy Shoppers API (OTE) API through Jentic.

What is a shopper in the GoDaddy API?

A shopper is a customer account entity in the GoDaddy system that owns domains, orders, and other resources. Each shopper has a unique shopper ID that can be used with the X-Shopper-Id header to perform operations on behalf of that account.

What is the GoDaddy OTE environment?

OTE (Operational Test Environment) is GoDaddy's sandbox for development and testing. It mirrors the production API but operates on test data and test accounts. No real charges or account changes occur in OTE.

Who can create subaccounts?

Only reseller accounts with appropriate permissions can create subaccounts via POST /v1/shoppers/subaccount. Standard customer accounts cannot create subaccounts. Reseller status is configured in the GoDaddy developer portal.

How do I use a shopper ID with other APIs?

Include the X-Shopper-Id header in requests to the Domains, Orders, or other GoDaddy APIs. This tells the API to perform the operation on behalf of that shopper account rather than the authenticated account.

Can I retrieve a list of all subaccounts I've created?

The specific endpoint for listing subaccounts depends on the API version and your account permissions. Contact GoDaddy developer support for the exact endpoint to list subaccounts under your reseller account.