Ote Godaddy API: Abuse
GoDaddy Abuse API Terms of Use: GoDaddy’s Abuse API is provided to simplify and standardize the abuse reporting experience. To help us streamline the review…
Developer tools#openapi#hosting
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
GoDaddy Abuse API Terms of Use: GoDaddy’s Abuse API is provided to simplify and standardize the abuse reporting experience. To help us streamline the review of abuse reports, you acknowledge and agree that your use of GoDaddy’s Abuse API is subject to the following quality metrics and terms of use. GoDaddy may, in its sole and absolute discretion, change or modify these terms, and such changes or modifications shall be effective immediately upon notice to you. Your use of GoDaddy’s Abuse API after such changes or modifications shall constitute your acceptance of these terms as last revised. If you do not agree to be bound by these terms as last revised, do not use (or continue to use) our Abuse API. As an Abuse API user, you must only submit abuse reports via the API portal and cease all email submissions, including but not limited, to phishing@godaddy.com, netabuse@godaddy.com, malware@godaddy.com, or spam@godaddy.com, etc. Any additional or duplicate submission outside of the API portal will be deprioritized for review. Submissions related to trademark, copyright or content issues may still be sent to trademarkclaims@godaddy.com, coyprightclaims@godaddy.com, and contentcomplaints@godaddy.com, respectively. Our Front of Site also describes other scenarios not covered by the API. When you submit abuse reports via GoDaddy’s Abuse API, you must ensure that you accurately categorize the abuse type of each report to match our definitions in the API documentations provided to you. Any submission that fails to match our definitions or is miscategorized will be marked as a false positive. Examples include, but are not limited to, submissions of trademark complaints marked as phishing or malware, or submissions of copyright complaints marked as phishing or malware, etc. If, at any time, the false positive rate of submissions exceeds 40% of your total submissions, as determined by GoDaddy, GoDaddy may in its sole discretion deprioritize any subsequent reports submitted by you and/or your organization. You acknowledge and agree that submitting every URL for a single domain is not necessary and will not expedite the review process. If your submissions exceed five (5) URLs for a single domain, your report will be marked as a duplicate submission taking into account that the final outcome of such submissions would yield the same result as the original report. GoDaddy may in its sole discretion deprioritize reports submitted by you and/or your organization in the event more than 20% of your submissions are classified as duplicate submissions. You further acknowledge and agree that our Customer Support lines are not intended to address abuse reporting matters or your use of GoDaddy’s Abuse API. Contacting Customer Support will not expedite the review process and may result in abuse reports being deprioritized, to be determined in our sole discretion. Should you have any questions about GoDaddy’s Abuse API or any of the terms and conditions set forth above, please contact abuseapisupport@godaddy.com.
Endpoints 3
v1
- GETList all abuse tickets ids that match user provided filters
/v1/abuse/tickets?type=A_RECORD&closed=false&sourceDomainOrIp=string&target=string&createdStart=string&createdEnd=string&limit=100&offset=0 - POSTCreate a new abuse ticket
/v1/abuse/tickets - GETReturn the abuse ticket data for a given ticket id
/v1/abuse/tickets/:ticketId
API details
- Authentication
- None declared in the description
- Operations
- 3 operations on 2 pathsGET 2POST 1
- Main resources
- v1 3
- Response formats
*/*- Description format
- OpenAPI 3.0.0, API version
1.0.0 - Links
- OpenAPI document
- Listed from
- APIs.guru OpenAPI Directory (CC0-1.0)
Source updated
How to test the Ote Godaddy API: Abuse in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Ote Godaddy API: Abuse collection, without the publisher's secrets.
- Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
- Send a requestPick an endpoint, for example “List all abuse tickets ids that match user provided filters” (GET /v1/abuse/tickets?type=A_RECORD&closed=false&sourceDomainOrIp=string&target=string&createdStart=string&createdEnd=string&limit=100&offset=0), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Ote Godaddy API: Abuse?
GoDaddy Abuse API Terms of Use: GoDaddy’s Abuse API is provided to simplify and standardize the abuse reporting experience. To help us streamline the review… It is listed under Developer tools and has 3 endpoints.
Who publishes the Ote Godaddy API: Abuse?
It is listed from Ote Godaddy's public API description (an OpenAPI document), not published by Ote Godaddy on Swastik Codes. Anyone who controls ote-godaddy.com can claim the profile by adding a DNS TXT record.
How do I authenticate with the Ote Godaddy API: Abuse?
Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.
How many endpoints does the Ote Godaddy API: Abuse have?
3 operations on 2 paths (2 GET, 1 POST). The largest groups are v1.
Is forking the Ote Godaddy API: Abuse free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.