> ## Documentation Index > Fetch the complete documentation index at: https://spotzee.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get URL lookup result > The URL threat lookup is bypassed. This endpoint returns listed: false without checking the URL against a threat source; the result does not establish that the URL is safe. ## OpenAPI ````yaml https://apix.spotzee.com/api/ext/openapi.json post /generic/email/malicious-url-lookup openapi: 3.1.0 info: title: Spotzee API version: '2026-04-28' description: >- Comprehensive API for email services, DNS management, AI tools, and marketing features. servers: - url: https://apix.spotzee.com/api/ext description: >- Extended API surface — sender-side utilities (DNS, AI, deliverability, generators). security: - BearerAuth: [] tags: - name: AI description: >- Sender-side AI utilities — generate copy, score subject lines, and draft message variants tailored to a contact or campaign brief. - name: Data description: >- Realistic-looking sample data for development and load testing — contacts, events, and segments shaped like production records without exposing real customer data. - name: DNS description: >- Inspect a domain’s sender posture — SPF, DKIM, DMARC, MX, and reverse-DNS records — and surface the gaps that put deliverability at risk. - name: Email description: >- Send-side validation and inspection — verify addresses, fingerprint MTAs, decode bounces, and check inbox-placement signals before a campaign goes out. - name: SMS description: Mobile-number validation and carrier lookup for SMS campaigns. - name: Text description: >- Text-quality utilities — spam-score grading, readability metrics, and subject-line scoring against deliverability heuristics. paths: /generic/email/malicious-url-lookup: post: tags: - Email summary: Get URL lookup result description: >- The URL threat lookup is bypassed. This endpoint returns listed: false without checking the URL against a threat source; the result does not establish that the URL is safe. operationId: checkMaliciousUrl requestBody: content: application/x-www-form-urlencoded: schema: type: object properties: url: type: string minLength: 1 format: uri required: - url responses: '200': description: Bypassed result; URL threats were not checked content: application/json: schema: type: object properties: status: type: string enum: - success data: description: Response data specific to the endpoint example: result: Operation completed successfully required: - status '400': description: Bad request - Invalid parameters content: application/json: schema: type: object properties: status: type: string enum: - error description: Indicates an error occurred error: type: string description: >- Human-readable error message. Mirrors the Main API envelope’s legacy `error` field; the canonical replacement is `message` + machine-readable `code` (see @spotzee/api-schemas/shared `ErrorResponse`). example: Invalid request parameters required: - status - error '401': description: Unauthorized - Invalid API key content: application/json: schema: type: object properties: status: type: string enum: - error description: Indicates an error occurred error: type: string description: >- Human-readable error message. Mirrors the Main API envelope’s legacy `error` field; the canonical replacement is `message` + machine-readable `code` (see @spotzee/api-schemas/shared `ErrorResponse`). example: Invalid request parameters required: - status - error '402': description: Payment Required - Quota exceeded content: application/json: schema: type: object properties: status: type: string enum: - error description: Indicates an error occurred error: type: string description: >- Human-readable error message. Mirrors the Main API envelope’s legacy `error` field; the canonical replacement is `message` + machine-readable `code` (see @spotzee/api-schemas/shared `ErrorResponse`). example: Invalid request parameters required: - status - error '500': description: Internal server error content: application/json: schema: type: object properties: status: type: string enum: - error description: Indicates an error occurred error: type: string description: >- Human-readable error message. Mirrors the Main API envelope’s legacy `error` field; the canonical replacement is `message` + machine-readable `code` (see @spotzee/api-schemas/shared `ErrorResponse`). example: Invalid request parameters required: - status - error '503': description: Service temporarily unavailable content: application/json: schema: type: object properties: status: type: string enum: - error description: Indicates an error occurred error: type: string description: >- Human-readable error message. Mirrors the Main API envelope’s legacy `error` field; the canonical replacement is `message` + machine-readable `code` (see @spotzee/api-schemas/shared `ErrorResponse`). example: Invalid request parameters required: - status - error '504': description: Gateway timeout - Request took too long content: application/json: schema: type: object properties: status: type: string enum: - error description: Indicates an error occurred error: type: string description: >- Human-readable error message. Mirrors the Main API envelope’s legacy `error` field; the canonical replacement is `message` + machine-readable `code` (see @spotzee/api-schemas/shared `ErrorResponse`). example: Invalid request parameters required: - status - error security: - BearerAuth: [] components: securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: API Key description: 'Bearer token authentication. Use format: Bearer YOUR_API_KEY' ````