Skip to content
Cloud infrastructure/devops

ote-godaddy.com:abuse

sandbox and mock API

<strong>GoDaddy Abuse API Terms of Use:</strong><p>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.</p><p>GoDaddy may, in its sole and absolute discretion, change or modify these te Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
3
Collections
-
Event types
-
Start this simulation
example request
curl https://your-ote-godaddy-abuse.slurry.io/v1/abuse/tickets \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

All 3.

  • GET/v1/abuse/tickets
  • POST/v1/abuse/tickets
  • GET/v1/abuse/tickets/{ticketId}