> ## 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.

# SERP Simulator

> Preview how your page's title and meta description will appear in Google search results, on desktop and mobile, with real Arial pixel-width measurements showing exactly where each one gets truncated.

[Try SERP Simulator in your browser →](https://iotools.cloud/tool/google-serp-snippet-simulator/)



## OpenAPI

````yaml https://api.iotools.cloud/v1/openapi post /v1/tool/google-serp-snippet-simulator
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/google-serp-snippet-simulator:
    post:
      tags:
        - Generators
      summary: SERP Simulator
      description: >-
        Preview how your page's title and meta description will appear in Google
        search results, on desktop and mobile, with real Arial pixel-width
        measurements showing exactly where each one gets truncated.


        [Try SERP Simulator in your browser
        →](https://iotools.cloud/tool/google-serp-snippet-simulator/)
      operationId: run_google_serp_snippet_simulator
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                title:
                  type: string
                  description: Page title
                description:
                  type: string
                  description: Meta description
                url:
                  type: string
                  description: Page URL
                query:
                  type: string
                  description: Search query
                device:
                  enum:
                    - desktop
                    - mobile
                  description: Device
                siteName:
                  type: string
                  description: Site name
                favicon:
                  type: boolean
                  description: Show favicon
                date:
                  type: string
                  description: Date prefix
                rating:
                  type: boolean
                  description: Show star rating
                ratingValue:
                  type: number
                  description: Rating
                  minimum: 0
                  maximum: 5
                ratingCount:
                  type: number
                  description: Review count
                descriptionLimit:
                  type: number
                  description: Description character limit
                  minimum: 80
                  maximum: 350
              required: []
            examples:
              desktop_result:
                summary: Desktop result
                value:
                  title: 'How to Bake Sourdough Bread at Home: A Beginner''s Guide'
                  description: >-
                    Everything a first-time baker needs to bake sourdough at
                    home: starter, schedule, shaping, and the oven setup that
                    finally gives you an open crumb.
                  url: https://example.com/guides/sourdough-for-beginners
                  query: sourdough beginners
                  device: desktop
                  siteName: ''
                  favicon: 'true'
                  date: ''
                  rating: ''
                  ratingValue: '4.5'
                  ratingCount: '128'
                  descriptionLimit: '160'
              mobile_result_with_rating:
                summary: Mobile result with rating
                value:
                  title: >-
                    Best Noise-Cancelling Headphones of 2026, Tested and Ranked
                    by Our Audio Team
                  description: >-
                    We tested 24 pairs over six months on planes, trains and
                    open-plan offices. These are the six worth your money, plus
                    the two to avoid entirely.
                  url: https://example.com/reviews/headphones/noise-cancelling
                  query: noise cancelling headphones
                  device: mobile
                  siteName: Example Reviews
                  favicon: 'true'
                  date: 12 Mar 2026
                  rating: 'true'
                  ratingValue: '4.5'
                  ratingCount: '128'
                  descriptionLimit: '160'
      responses:
        '200':
          description: Tool output
          content:
            application/json:
              examples:
                desktop_result:
                  summary: Desktop result
                  value:
                    tool: google-serp-snippet-simulator
                    tool_version: 1.0.1
                    outputs:
                      markup: >-
                        <div
                        style="font-family:arial,helvetica,sans-serif;background:#ffffff;border:1px
                        solid
                        #dfe1e5;border-radius:12px;padding:16px;width:632px;max-width:100%;box-sizing:border-box"><div
                        style="display:flex;align-items:center;margin-bottom:8px"><div
                        style="width:26px;height:26px;border-radius:50%;background:#e8f0fe;color:#1a73e8;font-size:13px;line-height:26px;text-align:center;flex:none;margin-right:12px">E</div><div><div
                        style="font-size:14px;line-height:18px;color:#202124">example.com</div><div
                        style="font-size:12px;line-height:16px;color:#4d5156">example.com
                        › guides › sourdough-for-beginners</div></div></div><div
                        style="font-size:20px;line-height:1.3;color:#1a0dab;margin-bottom:4px">How
                        to Bake Sourdough Bread at Home: A Beginner's
                        Guide</div><div
                        style="font-size:14px;line-height:1.58;color:#4d5156">Everything
                        a first-time baker needs to bake <b>sourdough</b> at
                        home: starter, schedule, shaping, and the oven setup
                        that finally gives you an open crumb.</div></div>
                      metrics:
                        - element: Title
                          measurement: 55 chars · 540 px of 600 px
                          status: Good
                        - element: Meta description
                          measurement: 147 chars · 2 of 2 lines
                          status: Good
                        - element: URL
                          measurement: 46 chars · 259 px
                          status: Good
                      metaTags: >-
                        <title>How to Bake Sourdough Bread at Home: A Beginner's
                        Guide</title>

                        <meta name="description" content="Everything a
                        first-time baker needs to bake sourdough at home:
                        starter, schedule, shaping, and the oven setup that
                        finally gives you an open crumb." />

                        <link rel="canonical"
                        href="https://example.com/guides/sourdough-for-beginners"
                        />
                    credits_used: 3
                    credits_remaining: null
                mobile_result_with_rating:
                  summary: Mobile result with rating
                  value:
                    tool: google-serp-snippet-simulator
                    tool_version: 1.0.1
                    outputs:
                      markup: >-
                        <div
                        style="font-family:arial,helvetica,sans-serif;background:#ffffff;border:1px
                        solid
                        #dfe1e5;border-radius:12px;padding:16px;width:395px;max-width:100%;box-sizing:border-box"><div
                        style="display:flex;align-items:center;margin-bottom:8px"><div
                        style="width:22px;height:22px;border-radius:50%;background:#e8f0fe;color:#1a73e8;font-size:11px;line-height:22px;text-align:center;flex:none;margin-right:12px">E</div><div><div
                        style="font-size:14px;line-height:18px;color:#202124">Example
                        Reviews</div><div
                        style="font-size:12px;line-height:16px;color:#4d5156">example.com
                        › reviews › headphones ›
                        noise-cancelling</div></div></div><div
                        style="font-size:16px;line-height:1.3;color:#1a0dab;margin-bottom:4px">Best
                        Noise-Cancelling Headphones of 2026,<br />Tested and
                        Ranked by Our Audio Team</div><div
                        style="font-size:14px;line-height:22px;color:#70757a"><span
                        style="color:#e7711b">★★★★☆</span> Rating: 4.5 · 128
                        reviews</div><div
                        style="font-size:14px;line-height:1.58;color:#4d5156"><span
                        style="color:#70757a">12 Mar 2026 — </span>We tested 24
                        pairs over six months on planes, trains and open-plan
                        offices. These are the six worth your money, plus the
                        two to avoid entirely.</div></div>
                      metrics:
                        - element: Title
                          measurement: 77 chars · 602 px of 726 px
                          status: Good
                        - element: Meta description
                          measurement: 143 chars · 3 of 3 lines
                          status: Good
                        - element: URL
                          measurement: 53 chars · 296 px
                          status: Good
                      metaTags: >-
                        <title>Best Noise-Cancelling Headphones of 2026, Tested
                        and Ranked by Our Audio Team</title>

                        <meta name="description" content="We tested 24 pairs
                        over six months on planes, trains and open-plan offices.
                        These are the six worth your money, plus the two to
                        avoid entirely." />

                        <link rel="canonical"
                        href="https://example.com/reviews/headphones/noise-cancelling"
                        />
                    credits_used: 3
                    credits_remaining: null
              schema:
                type: object
                required:
                  - tool
                  - tool_version
                  - outputs
                  - credits_used
                  - credits_remaining
                properties:
                  outputs:
                    type: object
                    properties:
                      metrics:
                        type: array
                        description: Length check
                        items:
                          type: object
                          properties:
                            element:
                              type: string
                              description: Element
                            measurement:
                              type: string
                              description: Measurement
                            status:
                              type: string
                              description: Status
                        x-iotools-columns:
                          - element
                          - measurement
                          - status
                      metaTags:
                        type: string
                        description: Meta tags
                      markup:
                        type: string
                        description: Preview HTML
                  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_…

````