> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iotools.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# SPF / DKIM / DMARC Record Generator

> Generate SPF, DKIM and DMARC DNS TXT records for your domain — pick email providers for SPF, count DNS lookups against the RFC 7208 limit, build a DKIM record from a public key, and set a DMARC rollout policy.

[Try SPF / DKIM / DMARC Record Generator in your browser →](https://iotools.cloud/tool/spf-dkim-dmarc-record-generator/)



## OpenAPI

````yaml https://api.iotools.cloud/v1/openapi post /v1/tool/spf-dkim-dmarc-record-generator
openapi: 3.1.0
info:
  title: iotools.cloud API
  version: 1.0.0
  description: >-
    Run any iotools.cloud tool over HTTP.


    Authenticate with `Authorization: Bearer iot_live_…`.


    **Only `POST /v1/tool/{slug}` costs credits.** Every GET here — the catalog,
    a tool's schema, your balance — is free. A tool call is charged its own
    weight or your plan's per-call minimum, whichever is larger;
    `x-iotools-credit-cost` on each operation is quoted at the free-tier
    minimum, and `GET /v1/tools/list` returns the exact figure for your key.
    `GET /v1/me/credits` reports what you have left, and `GET /v1/me/usage`
    reports what it went on.


    Failures are RFC 9457 problem documents — branch on `code`.
servers:
  - url: https://api.iotools.cloud
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Catalog
    description: Find a tool and read its contract. Free.
  - name: Converters
    description: >-
      Convert between formats, encodings, and units — Base64, CSV and JSON,
      timestamps, and more. Fast, free, and processed right in your browser.
  - name: Formatters
    description: >-
      Format, beautify, minify, and validate code and data — JSON, HTML, CSS,
      SQL, and regex. Clean up messy input in one click, with nothing to upload.
  - name: Generators
    description: >-
      Generate exactly what you need and on demand — passwords, UUIDs, QR codes,
      hashes, random numbers, and more. Secure, instant, and free.
  - name: Calculators
    description: >-
      Crunch the numbers fast — from everyday math to specialized conversions
      and unit work. Free online calculators that run entirely in your browser.
  - name: Editors
    description: >-
      Edit and transform text, code, and images with quick, focused editors that
      run entirely in your browser — nothing to install, and no sign-up needed.
  - name: Utilities
    description: >-
      Everyday developer and web utilities — DNS and IP lookups, redirect and
      certificate checkers, and other quick diagnostics. Free and
      privacy-friendly.
  - name: Account
    description: Your key's allowance, limits and usage history.
paths:
  /v1/tool/spf-dkim-dmarc-record-generator:
    post:
      tags:
        - Generators
      summary: SPF / DKIM / DMARC Record Generator
      description: >-
        Generate SPF, DKIM and DMARC DNS TXT records for your domain — pick
        email providers for SPF, count DNS lookups against the RFC 7208 limit,
        build a DKIM record from a public key, and set a DMARC rollout policy.


        [Try SPF / DKIM / DMARC Record Generator in your browser
        →](https://iotools.cloud/tool/spf-dkim-dmarc-record-generator/)
      operationId: run_spf_dkim_dmarc_record_generator
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                domain:
                  type: string
                  description: Domain
                ttl:
                  type: number
                  description: TTL
                  minimum: 60
                spfEnable:
                  type: boolean
                  description: Generate SPF record
                spfGoogle:
                  type: boolean
                  description: Google Workspace (include:_spf.google.com)
                spfMicrosoft:
                  type: boolean
                  description: Microsoft 365 (include:spf.protection.outlook.com)
                spfSendgrid:
                  type: boolean
                  description: SendGrid (include:sendgrid.net)
                spfMailchimp:
                  type: boolean
                  description: Mailchimp (include:servers.mcsv.net)
                spfMailgun:
                  type: boolean
                  description: Mailgun (include:mailgun.org)
                spfSes:
                  type: boolean
                  description: Amazon SES (include:amazonses.com)
                spfZoho:
                  type: boolean
                  description: Zoho Mail (include:zoho.com)
                spfPostmark:
                  type: boolean
                  description: Postmark (include:spf.mtasv.net)
                spfMechA:
                  type: boolean
                  description: Authorize A records of this domain (a)
                spfMechMx:
                  type: boolean
                  description: Authorize MX records of this domain (mx)
                spfIp4:
                  type: string
                  description: Extra IPv4
                spfIp6:
                  type: string
                  description: Extra IPv6
                spfCustomIncludes:
                  type: string
                  description: Extra includes
                spfAll:
                  enum:
                    - ~all
                    - '-all'
                    - '?all'
                  description: All Mechanism
                dkimEnable:
                  type: boolean
                  description: Generate DKIM record
                dkimSelector:
                  type: string
                  description: Selector
                dkimKeyType:
                  enum:
                    - rsa
                    - ed25519
                  description: Key Type
                dkimPublicKey:
                  type: string
                  description: Public Key (base64)
                dmarcEnable:
                  type: boolean
                  description: Generate DMARC record
                dmarcPolicy:
                  enum:
                    - none
                    - quarantine
                    - reject
                  description: Policy
                dmarcSubdomainPolicy:
                  enum:
                    - inherit
                    - none
                    - quarantine
                    - reject
                  description: Subdomain Policy
                dmarcPct:
                  type: number
                  description: Percent (pct)
                  minimum: 1
                  maximum: 100
                dmarcRua:
                  type: string
                  description: Aggregate (rua)
                dmarcRuf:
                  type: string
                  description: Forensic (ruf)
                dmarcAdkim:
                  enum:
                    - r
                    - s
                  description: DKIM Alignment
                dmarcAspf:
                  enum:
                    - r
                    - s
                  description: SPF Alignment
              required: []
            examples:
              example_com_with_google_workspace_strict_spf:
                summary: example.com with Google Workspace + strict SPF
                value:
                  domain: example.com
                  ttl: '3600'
                  spfEnable: 'true'
                  spfGoogle: 'true'
                  spfAll: '-all'
                  dkimEnable: 'true'
                  dkimSelector: google
                  dkimKeyType: rsa
                  dkimPublicKey: >-
                    MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxQy3p+xQUz8mWvCgZJ7iWZxYJxL5n3X0sIVu0vJq5x2Y9wYJjJ2KhJk3l8xWzXvFq+8K+R4mPp1mZ7r4u3qC6vY0nQXk6mWdY+bN0L1JaTAGtO/8XPV2W2t3hZx0BUmQp4cYj7P2qJaXQwIDAQAB
                  dmarcEnable: 'true'
                  dmarcPolicy: quarantine
                  dmarcSubdomainPolicy: inherit
                  dmarcPct: '50'
                  dmarcRua: dmarc-reports@example.com
      responses:
        '200':
          description: Tool output
          content:
            application/json:
              examples:
                example_com_with_google_workspace_strict_spf:
                  summary: example.com with Google Workspace + strict SPF
                  value:
                    tool: spf-dkim-dmarc-record-generator
                    tool_version: 1.0.1
                    outputs:
                      spfOutput: |-
                        ━━━ SPF Record ━━━━━━━━━━━━━━━━━━
                          Name:    @  (or example.com.)
                          Type:    TXT
                          TTL:     3600
                          Value:
                            v=spf1 include:_spf.google.com -all

                        ━━━ DNS Lookups ━━━━━━━━━━━━━━━━━
                          ✓ OK - 1/10 lookups

                          Breakdown:
                          include:_spf.google.com  (Google Workspace) - 1 lookup

                        ━━━ How to Add ━━━━━━━━━━━━━━━━━━
                          Create a TXT record at your DNS provider with:
                            Name:  @ (root)
                            Type:  TXT
                            TTL:   3600
                            Value: the v=spf1 ... line above
                          Only one SPF (v=spf1) record is allowed per domain - merge if you already have one.
                      dkimOutput: |-
                        ━━━ DKIM Record ━━━━━━━━━━━━━━━━━
                          Name:    google._domainkey.example.com
                          Type:    TXT
                          TTL:     3600
                          Value:
                            v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxQy3p+xQUz8mWvCgZJ7iWZxYJxL5n3X0sIVu0vJq5x2Y9wYJjJ2KhJk3l8xWzXvFq+8K+R4mPp1mZ7r4u3qC6vY0nQXk6mWdY+bN0L1JaTAGtO/8XPV2W2t3hZx0BUmQp4cYj7P2qJaXQwIDAQAB

                        ━━━ Key Info ━━━━━━━━━━━━━━━━━━━━
                          Selector:   google
                          Algorithm:  RSA
                          Key length: 192 base64 chars (~144 bytes)

                        ━━━ How to Add ━━━━━━━━━━━━━━━━━━
                          Create a TXT record at your DNS provider with:
                            Name:  google._domainkey
                            Type:  TXT
                            TTL:   3600
                            Value: the v=DKIM1 ... line above
                          Use selector "google" in your outgoing mail server's DKIM signing config.
                      dmarcOutput: |-
                        ━━━ DMARC Record ━━━━━━━━━━━━━━━━
                          Name:    _dmarc.example.com
                          Type:    TXT
                          TTL:     3600
                          Value:
                            v=DMARC1; p=quarantine; pct=50; rua=mailto:dmarc-reports@example.com

                        ━━━ Policy ━━━━━━━━━━━━━━━━━━━━━━
                          Main (p):       quarantine  (failing mail goes to spam / quarantine)
                          Subdomain (sp): inherits p=quarantine
                          Enforced on:    50% of failing mail
                          DKIM align:     relaxed (adkim=r)
                          SPF align:      relaxed (aspf=r)

                        ━━━ Reporting ━━━━━━━━━━━━━━━━━━━
                          Aggregate (rua): mailto:dmarc-reports@example.com
                          Forensic (ruf):  none

                        ━━━ Recommended Rollout ━━━━━━━━━
                          1. p=none + rua=  -> collect reports for 2-4 weeks
                          2. p=quarantine pct=10  -> ramp pct 10 -> 25 -> 50 -> 100
                          3. p=reject pct=100  -> full enforcement
                          Authenticate every legitimate sender (SPF + DKIM) before moving past step 1.

                        ━━━ How to Add ━━━━━━━━━━━━━━━━━━
                          Create a TXT record at your DNS provider with:
                            Name:  _dmarc
                            Type:  TXT
                            TTL:   3600
                            Value: the v=DMARC1 ... line above
                    credits_used: 3
                    credits_remaining: null
              schema:
                type: object
                required:
                  - tool
                  - tool_version
                  - outputs
                  - credits_used
                  - credits_remaining
                properties:
                  outputs:
                    type: object
                    properties:
                      spfOutput:
                        type: string
                        description: SPF Record
                      dkimOutput:
                        type: string
                        description: DKIM Record
                      dmarcOutput:
                        type: string
                        description: DMARC Record
                  tool:
                    type: string
                    description: The tool's slug, echoing the {slug} in the request path.
                  tool_version:
                    type: string
                    description: Output-contract version for this tool.
                  credits_used:
                    type: integer
                    description: >-
                      Credits this call consumed, after any settlement refund. 0
                      when metering is disabled.
                  credits_remaining:
                    type:
                      - integer
                      - 'null'
                    description: >-
                      Credits left in the current monthly allowance, or null
                      when metering is disabled.
                  request_id:
                    type: string
                    description: Correlation id, also sent as x-request-id.
        '400':
          $ref: '#/components/responses/ValidationError'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '402':
          $ref: '#/components/responses/InsufficientCredits'
        '403':
          $ref: '#/components/responses/ToolNotAllowed'
        '404':
          $ref: '#/components/responses/ToolNotFound'
        '413':
          $ref: '#/components/responses/PayloadTooLarge'
        '429':
          $ref: '#/components/responses/RateLimited'
        '500':
          $ref: '#/components/responses/ToolFailed'
        '503':
          $ref: '#/components/responses/ToolDisabled'
      security:
        - bearerAuth: []
components:
  responses:
    ValidationError:
      description: Invalid request.
      content:
        application/problem+json:
          schema:
            type: object
            description: >-
              RFC 9457 problem document, served as application/problem+json.
              Branch on `code`; `title` is human prose and may be reworded
              without notice. Some failures add extension members — `fields` on
              validation errors, `retry_after` on 429s,
              `credits_used`/`credits_remaining` on billing-adjacent failures —
              documented on the responses that carry them.
            required:
              - type
              - title
              - status
              - code
            properties:
              type:
                type: string
                format: uri
                description: Stable documentation URI for this failure.
                examples:
                  - https://iotools.cloud/docs/errors/validation_error
              title:
                type: string
                description: Short human-readable summary of the failure.
                examples:
                  - Invalid request
              status:
                type: integer
                description: HTTP status code, matching the response's own status.
              code:
                type: string
                description: >-
                  Stable machine-readable error code — branch on this, not
                  `title`.
                enum:
                  - validation_error
              detail:
                type: string
                description: Human explanation of this occurrence.
              request_id:
                type: string
                description: Correlation id, also sent as x-request-id.
              fields:
                type:
                  - object
                  - string
                additionalProperties:
                  type: string
                description: >-
                  What failed: a map of field name → message. Absent when the
                  body itself is malformed; a single string when the failure
                  isn't tied to one field.
          example:
            type: https://iotools.cloud/docs/errors/validation_error
            title: Invalid request
            status: 400
            code: validation_error
            detail: One or more inputs are invalid — see `fields`.
            request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11
            fields:
              inputString: Required
    Unauthorized:
      description: Missing or invalid API key.
      content:
        application/problem+json:
          schema:
            type: object
            description: >-
              RFC 9457 problem document, served as application/problem+json.
              Branch on `code`; `title` is human prose and may be reworded
              without notice. Some failures add extension members — `fields` on
              validation errors, `retry_after` on 429s,
              `credits_used`/`credits_remaining` on billing-adjacent failures —
              documented on the responses that carry them.
            required:
              - type
              - title
              - status
              - code
            properties:
              type:
                type: string
                format: uri
                description: Stable documentation URI for this failure.
                examples:
                  - https://iotools.cloud/docs/errors/invalid_api_key
              title:
                type: string
                description: Short human-readable summary of the failure.
                examples:
                  - Invalid API key
              status:
                type: integer
                description: HTTP status code, matching the response's own status.
              code:
                type: string
                description: >-
                  Stable machine-readable error code — branch on this, not
                  `title`.
                enum:
                  - invalid_api_key
              detail:
                type: string
                description: Human explanation of this occurrence.
              request_id:
                type: string
                description: Correlation id, also sent as x-request-id.
          example:
            type: https://iotools.cloud/docs/errors/invalid_api_key
            title: Invalid API key
            status: 401
            code: invalid_api_key
            detail: 'Provide ''Authorization: Bearer <key>''.'
            request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11
    InsufficientCredits:
      description: Monthly credit allowance exhausted.
      content:
        application/problem+json:
          schema:
            type: object
            description: >-
              RFC 9457 problem document, served as application/problem+json.
              Branch on `code`; `title` is human prose and may be reworded
              without notice. Some failures add extension members — `fields` on
              validation errors, `retry_after` on 429s,
              `credits_used`/`credits_remaining` on billing-adjacent failures —
              documented on the responses that carry them.
            required:
              - type
              - title
              - status
              - code
            properties:
              type:
                type: string
                format: uri
                description: Stable documentation URI for this failure.
                examples:
                  - https://iotools.cloud/docs/errors/insufficient_credits
              title:
                type: string
                description: Short human-readable summary of the failure.
                examples:
                  - Insufficient credits
              status:
                type: integer
                description: HTTP status code, matching the response's own status.
              code:
                type: string
                description: >-
                  Stable machine-readable error code — branch on this, not
                  `title`.
                enum:
                  - insufficient_credits
              detail:
                type: string
                description: Human explanation of this occurrence.
              request_id:
                type: string
                description: Correlation id, also sent as x-request-id.
              credits_used:
                type: integer
                description: Always 0 — a refused call charges nothing.
              credits_remaining:
                type: integer
                description: Credits left in the allowance — fewer than this call costs.
          example:
            type: https://iotools.cloud/docs/errors/insufficient_credits
            title: Insufficient credits
            status: 402
            code: insufficient_credits
            detail: This call costs 1 credit and 0 remain in this month's allowance.
            request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11
            credits_used: 0
            credits_remaining: 0
    ToolNotAllowed:
      description: Tool exists but has no API surface.
      content:
        application/problem+json:
          schema:
            type: object
            description: >-
              RFC 9457 problem document, served as application/problem+json.
              Branch on `code`; `title` is human prose and may be reworded
              without notice. Some failures add extension members — `fields` on
              validation errors, `retry_after` on 429s,
              `credits_used`/`credits_remaining` on billing-adjacent failures —
              documented on the responses that carry them.
            required:
              - type
              - title
              - status
              - code
            properties:
              type:
                type: string
                format: uri
                description: Stable documentation URI for this failure.
                examples:
                  - https://iotools.cloud/docs/errors/tool_not_allowed
              title:
                type: string
                description: Short human-readable summary of the failure.
                examples:
                  - Tool not available over the API
              status:
                type: integer
                description: HTTP status code, matching the response's own status.
              code:
                type: string
                description: >-
                  Stable machine-readable error code — branch on this, not
                  `title`.
                enum:
                  - tool_not_allowed
              detail:
                type: string
                description: Human explanation of this occurrence.
              request_id:
                type: string
                description: Correlation id, also sent as x-request-id.
          example:
            type: https://iotools.cloud/docs/errors/tool_not_allowed
            title: Tool not available over the API
            status: 403
            code: tool_not_allowed
            detail: >-
              "Background Remover" is available on iotools.cloud but has no API
              endpoint.
            request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11
    ToolNotFound:
      description: No such tool.
      content:
        application/problem+json:
          schema:
            type: object
            description: >-
              RFC 9457 problem document, served as application/problem+json.
              Branch on `code`; `title` is human prose and may be reworded
              without notice. Some failures add extension members — `fields` on
              validation errors, `retry_after` on 429s,
              `credits_used`/`credits_remaining` on billing-adjacent failures —
              documented on the responses that carry them.
            required:
              - type
              - title
              - status
              - code
            properties:
              type:
                type: string
                format: uri
                description: Stable documentation URI for this failure.
                examples:
                  - https://iotools.cloud/docs/errors/tool_not_found
              title:
                type: string
                description: Short human-readable summary of the failure.
                examples:
                  - Tool not found
              status:
                type: integer
                description: HTTP status code, matching the response's own status.
              code:
                type: string
                description: >-
                  Stable machine-readable error code — branch on this, not
                  `title`.
                enum:
                  - tool_not_found
              detail:
                type: string
                description: Human explanation of this occurrence.
              request_id:
                type: string
                description: Correlation id, also sent as x-request-id.
          example:
            type: https://iotools.cloud/docs/errors/tool_not_found
            title: Tool not found
            status: 404
            code: tool_not_found
            detail: No tool with that slug. See GET /v1/tools/list.
            request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11
    PayloadTooLarge:
      description: Body too large.
      content:
        application/problem+json:
          schema:
            type: object
            description: >-
              RFC 9457 problem document, served as application/problem+json.
              Branch on `code`; `title` is human prose and may be reworded
              without notice. Some failures add extension members — `fields` on
              validation errors, `retry_after` on 429s,
              `credits_used`/`credits_remaining` on billing-adjacent failures —
              documented on the responses that carry them.
            required:
              - type
              - title
              - status
              - code
            properties:
              type:
                type: string
                format: uri
                description: Stable documentation URI for this failure.
                examples:
                  - https://iotools.cloud/docs/errors/payload_too_large
              title:
                type: string
                description: Short human-readable summary of the failure.
                examples:
                  - Payload too large
              status:
                type: integer
                description: HTTP status code, matching the response's own status.
              code:
                type: string
                description: >-
                  Stable machine-readable error code — branch on this, not
                  `title`.
                enum:
                  - payload_too_large
              detail:
                type: string
                description: Human explanation of this occurrence.
              request_id:
                type: string
                description: Correlation id, also sent as x-request-id.
          example:
            type: https://iotools.cloud/docs/errors/payload_too_large
            title: Payload too large
            status: 413
            code: payload_too_large
            detail: Request body exceeds this tool's size limit.
            request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11
    RateLimited:
      description: Per-minute rate limit exceeded.
      headers:
        Retry-After:
          description: Seconds to wait before retrying (RFC 9110 delta-seconds).
          schema:
            type: integer
      content:
        application/problem+json:
          schema:
            type: object
            description: >-
              RFC 9457 problem document, served as application/problem+json.
              Branch on `code`; `title` is human prose and may be reworded
              without notice. Some failures add extension members — `fields` on
              validation errors, `retry_after` on 429s,
              `credits_used`/`credits_remaining` on billing-adjacent failures —
              documented on the responses that carry them.
            required:
              - type
              - title
              - status
              - code
            properties:
              type:
                type: string
                format: uri
                description: Stable documentation URI for this failure.
                examples:
                  - https://iotools.cloud/docs/errors/rate_limited
              title:
                type: string
                description: Short human-readable summary of the failure.
                examples:
                  - Rate limit exceeded
              status:
                type: integer
                description: HTTP status code, matching the response's own status.
              code:
                type: string
                description: >-
                  Stable machine-readable error code — branch on this, not
                  `title`.
                enum:
                  - rate_limited
              detail:
                type: string
                description: Human explanation of this occurrence.
              request_id:
                type: string
                description: Correlation id, also sent as x-request-id.
              retry_after:
                type: integer
                description: >-
                  Seconds until the window resets — the same value as the
                  `Retry-After` header.
          example:
            type: https://iotools.cloud/docs/errors/rate_limited
            title: Rate limit exceeded
            status: 429
            code: rate_limited
            detail: Too many requests. Retry in 30s.
            request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11
            retry_after: 30
    ToolFailed:
      description: Tool failed to run.
      content:
        application/problem+json:
          schema:
            type: object
            description: >-
              RFC 9457 problem document, served as application/problem+json.
              Branch on `code`; `title` is human prose and may be reworded
              without notice. Some failures add extension members — `fields` on
              validation errors, `retry_after` on 429s,
              `credits_used`/`credits_remaining` on billing-adjacent failures —
              documented on the responses that carry them.
            required:
              - type
              - title
              - status
              - code
            properties:
              type:
                type: string
                format: uri
                description: Stable documentation URI for this failure.
                examples:
                  - https://iotools.cloud/docs/errors/processing_error
                  - https://iotools.cloud/docs/errors/internal_error
              title:
                type: string
                description: Short human-readable summary of the failure.
                examples:
                  - Tool failed to run
                  - Internal error
              status:
                type: integer
                description: HTTP status code, matching the response's own status.
              code:
                type: string
                description: >-
                  Stable machine-readable error code — branch on this, not
                  `title`.
                enum:
                  - processing_error
                  - internal_error
              detail:
                type: string
                description: Human explanation of this occurrence.
              request_id:
                type: string
                description: Correlation id, also sent as x-request-id.
              credits_used:
                type: integer
                description: >-
                  Always 0 on `processing_error` — a failed run is refunded,
                  floor included.
              credits_remaining:
                type: integer
                description: >-
                  Credits left after the refund. Absent when metering is
                  disabled.
          example:
            type: https://iotools.cloud/docs/errors/processing_error
            title: Tool failed to run
            status: 500
            code: processing_error
            detail: The tool failed to run. Please try again.
            request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11
            credits_used: 0
    ToolDisabled:
      description: Tool temporarily disabled.
      content:
        application/problem+json:
          schema:
            type: object
            description: >-
              RFC 9457 problem document, served as application/problem+json.
              Branch on `code`; `title` is human prose and may be reworded
              without notice. Some failures add extension members — `fields` on
              validation errors, `retry_after` on 429s,
              `credits_used`/`credits_remaining` on billing-adjacent failures —
              documented on the responses that carry them.
            required:
              - type
              - title
              - status
              - code
            properties:
              type:
                type: string
                format: uri
                description: Stable documentation URI for this failure.
                examples:
                  - https://iotools.cloud/docs/errors/tool_disabled
                  - https://iotools.cloud/docs/errors/api_unconfigured
              title:
                type: string
                description: Short human-readable summary of the failure.
                examples:
                  - Tool temporarily disabled
                  - API not configured
              status:
                type: integer
                description: HTTP status code, matching the response's own status.
              code:
                type: string
                description: >-
                  Stable machine-readable error code — branch on this, not
                  `title`.
                enum:
                  - tool_disabled
                  - api_unconfigured
              detail:
                type: string
                description: Human explanation of this occurrence.
              request_id:
                type: string
                description: Correlation id, also sent as x-request-id.
          example:
            type: https://iotools.cloud/docs/errors/tool_disabled
            title: Tool temporarily disabled
            status: 503
            code: tool_disabled
            detail: This tool is temporarily unavailable. Try again shortly.
            request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: iot_live_…

````