How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

GoDaddy Abuse API

The Abuse API from GoDaddy — 4 operation(s) for abuse.

GoDaddy Abuse API is one of 13 APIs that GoDaddy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Abuse. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 6 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.ote-godaddy.com.

6 operations 4 paths 10 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.godaddy.com
Resource Areas
1

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Abuse 6
GET
/v1/abuse/tickets
List all abuse tickets ids that match user provided filters
getTickets 8 params → 200401403422
POST
/v1/abuse/tickets
Create a new abuse ticket
createTicket body → 201401403422
GET
/v1/abuse/tickets/{ticketId}
Return the abuse ticket data for a given ticket id
getTicketInfo 1 param → 200401403404
GET
/v2/abuse/tickets
List all abuse tickets ids that match user provided filters
getTicketsV2 8 params → 200401403422
POST
/v2/abuse/tickets
Create a new abuse ticket
createTicketV2 body → 201401403422
GET
/v2/abuse/tickets/{ticketId}
Return the abuse ticket data for a given ticket id
getTicketInfoV2 1 param → 200401403404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are AbuseTicketLegacy (9 properties), Pagination (5 properties), AbuseTicketCreateBase (4 properties), Error (4 properties). Each schema is shown below with its type and property counts.

AbuseTicketCreateBase
object
4 properties 1 required
AbuseTicketLegacy
object
The associated fields returned, given a unique abuse ticket id
9 properties 9 required
AbuseTicket
AbuseTicketCreate
1 required
Error
object
4 properties 1 required
ErrorField
object
4 properties 2 required
AbuseTicketCreateLegacy
1 required
AbuseTicketList
object
2 properties 1 required
Pagination
object
5 properties
AbuseTicketId
object
The primary key of a newly created abuse ticket
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

godaddy-abuse-api-openapi.yml Raw ↑

Other APIs GoDaddy publishes across the network.

GoDaddy Actions API
GoDaddy Contacts API
GoDaddy Domains API
GoDaddy Expiry Auctions: Registrar Partners API
GoDaddy Notifications API
GoDaddy Agreements API
GoDaddy Certificates API
GoDaddy Countries API
GoDaddy Customers API
GoDaddy Orders API
GoDaddy Shoppers API
GoDaddy Subscriptions API
Where this information came from

This is an independent, third-party profile of GoDaddy Abuse API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.