{"files":{"SKILL.md":"---\nname: abuse-api\ndescription: \"Abuse API skill. Use when working with Abuse for abuse. Covers 6 endpoints.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# Abuse API\nAPI version: 2.0.0\n\n## Auth\nNo authentication required.\n\n## Base URL\nhttps://api.ote-godaddy.com\n\n## Setup\n1. No auth setup needed\n2. GET /v1/abuse/tickets -- verify access\n3. POST /v1/abuse/tickets -- create first tickets\n\n## Endpoints\n\n6 endpoints across 1 groups. See references/api-spec.lap for full details.\n\n### abuse\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /v1/abuse/tickets | List all abuse tickets ids that match user provided filters |\n| POST | /v1/abuse/tickets | Create a new abuse ticket |\n| GET | /v1/abuse/tickets/{ticketId} | Return the abuse ticket data for a given ticket id |\n| GET | /v2/abuse/tickets | List all abuse tickets ids that match user provided filters |\n| POST | /v2/abuse/tickets | Create a new abuse ticket |\n| GET | /v2/abuse/tickets/{ticketId} | Return the abuse ticket data for a given ticket id |\n\n## Common Questions\n\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"List all tickets?\" -> GET /v1/abuse/tickets\n- \"Create a ticket?\" -> POST /v1/abuse/tickets\n- \"Get ticket details?\" -> GET /v1/abuse/tickets/{ticketId}\n- \"List all tickets?\" -> GET /v2/abuse/tickets\n- \"Create a ticket?\" -> POST /v2/abuse/tickets\n- \"Get ticket details?\" -> GET /v2/abuse/tickets/{ticketId}\n\n## Response Tips\n- Check response schemas in references/api-spec.lap for field details\n- List endpoints may support pagination; check for limit, offset, or cursor params\n- Create/update endpoints typically return the created/updated object\n\n## CLI\n\n```bash\n# Update this spec to the latest version\nnpx @lap-platform/lapsh get abuse-api -o references/api-spec.lap\n\n# Search for related APIs\nnpx @lap-platform/lapsh search abuse-api\n```\n\n## References\n- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas\n\n> Generated from the official API spec by [LAP](https://lap.sh)\n","references/api-spec.lap":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api Abuse API\n@base https://api.ote-godaddy.com\n@version 2.0.0\n@endpoints 6\n@toc abuse(6)\n\n@endpoint GET /v1/abuse/tickets\n@desc List all abuse tickets ids that match user provided filters\n@optional {type: any # The type of abuse., closed: any # Is this abuse ticket closed?, sourceDomainOrIp: any # The domain name or ip address the abuse originated from, target: any # The brand/company the abuse is targeting. ie: brand name/bank name, createdStart: any # The earliest abuse ticket creation date to pull abuse tickets for, createdEnd: any # The latest abuse ticket creation date to pull abuse tickets for, limit: any # Number of abuse ticket numbers to return., offset: any # The earliest result set record number to pull abuse tickets for}\n@returns(200) Success\n@errors {401: Authentication info not sent or invalid, 403: Authenticated user is not allowed access, 422: Error}\n\n@endpoint POST /v1/abuse/tickets\n@desc Create a new abuse ticket\n@required {body: any # The endpoint which allows the Reporter to create a new abuse ticket}\n@returns(201) Success\n@errors {401: Authentication info not sent or invalid, 403: Authenticated user is not allowed access, 422: Error}\n\n@endpoint GET /v1/abuse/tickets/{ticketId}\n@desc Return the abuse ticket data for a given ticket id\n@required {ticketId: any # A unique abuse ticket identifier}\n@returns(200) Success\n@errors {401: Authentication info not sent or invalid, 403: Authenticated user is not allowed access, 404: Invalid ticket id provided}\n\n@endpoint GET /v2/abuse/tickets\n@desc List all abuse tickets ids that match user provided filters\n@optional {type: any # The type of abuse., closed: any # Is this abuse ticket closed?, sourceDomainOrIp: any # The domain name or ip address the abuse originated from, target: any # The brand/company the abuse is targeting. ie: brand name/bank name, createdStart: any # The earliest abuse ticket creation date to pull abuse tickets for, createdEnd: any # The latest abuse ticket creation date to pull abuse tickets for, limit: any # Number of abuse ticket numbers to return., offset: any # The earliest result set record number to pull abuse tickets for}\n@returns(200) Success\n@errors {401: Authentication info not sent or invalid, 403: Authenticated user is not allowed access, 422: Error}\n\n@endpoint POST /v2/abuse/tickets\n@desc Create a new abuse ticket\n@required {body: any # The endpoint which allows the Reporter to create a new abuse ticket}\n@returns(201) Success\n@errors {401: Authentication info not sent or invalid, 403: Authenticated user is not allowed access, 422: Error}\n\n@endpoint GET /v2/abuse/tickets/{ticketId}\n@desc Return the abuse ticket data for a given ticket id\n@required {ticketId: any # A unique abuse ticket identifier}\n@returns(200) Success\n@errors {401: Authentication info not sent or invalid, 403: Authenticated user is not allowed access, 404: Invalid ticket id provided}\n\n@end\n"}}