> ## 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. # DNS Zone File Parser > Paste a BIND zone file and read it as a table: every record with its owner name fully qualified, its inherited TTL resolved, and its type and rdata split out. Honours $ORIGIN, $TTL and multi-line SOA blocks, flags the classic mistakes (missing SOA, a CNAME sharing a name, a target missing its trailing dot), and exports to CSV or JSON. Runs entirely in your browser — no DNS lookups. [Try DNS Zone File Parser in your browser →](https://iotools.cloud/tool/dns-zone-file-parser/) ## OpenAPI ````yaml https://api.iotools.cloud/v1/openapi post /v1/tool/dns-zone-file-parser 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/dns-zone-file-parser: post: tags: - Utilities summary: DNS Zone File Parser description: >- Paste a BIND zone file and read it as a table: every record with its owner name fully qualified, its inherited TTL resolved, and its type and rdata split out. Honours $ORIGIN, $TTL and multi-line SOA blocks, flags the classic mistakes (missing SOA, a CNAME sharing a name, a target missing its trailing dot), and exports to CSV or JSON. Runs entirely in your browser — no DNS lookups. [Try DNS Zone File Parser in your browser →](https://iotools.cloud/tool/dns-zone-file-parser/) operationId: run_dns_zone_file_parser requestBody: required: false content: application/json: schema: type: object properties: zoneFile: type: string description: Zone file origin: type: string description: Origin defaultTtl: type: string description: Default TTL ttlFormat: enum: - seconds - human description: TTL display required: [] examples: full_zone_soa_inherited_owner_relative_mx_target: summary: Full zone (SOA, inherited owner, relative MX target) value: zoneFile: |- $ORIGIN example.com. $TTL 1h @ IN SOA ns1.example.com. hostmaster.example.com. ( 2026072601 ; serial 7200 ; refresh 900 ; retry 1209600 ; expire 3600 ) ; minimum @ IN NS ns1.example.com. IN NS ns2.example.com. @ IN A 192.0.2.10 @ 300 IN AAAA 2001:db8::10 www IN CNAME @ mail IN A 192.0.2.20 @ IN MX 10 mail @ IN TXT "v=spf1 ip4:192.0.2.20 -all" _sip._tcp IN SRV 10 5 5060 sipserver.example.com. @ IN CAA 0 issue "letsencrypt.org" zone_with_mistakes_cname_conflict_duplicate_a: summary: Zone with mistakes (CNAME conflict, duplicate A) value: zoneFile: >- $ORIGIN example.net. $TTL 300 @ IN SOA ns1.example.net. admin.example.net. ( 1 7200 900 1209600 3600 ) @ IN NS ns1.example.net. shop IN CNAME storefront.example.net. shop IN TXT "verification=abc123" blog IN A 198.51.100.5 blog IN A 198.51.100.5 no_origin_or_ttl_filled_in_from_the_options: summary: No $ORIGIN or $TTL — filled in from the options value: zoneFile: "@\t3600\tIN\tSOA\tns1.example.org. admin.example.org. ( 1 7200 900 1209600 3600 )\n@\tIN\tNS\tns1.example.org.\nwww\tIN\tA\t203.0.113.7" origin: example.org defaultTtl: 90m ttlFormat: human responses: '200': description: Tool output content: application/json: examples: full_zone_soa_inherited_owner_relative_mx_target: summary: Full zone (SOA, inherited owner, relative MX target) value: tool: dns-zone-file-parser tool_version: 1.0.1 outputs: summary: - field: Origin value: example.com. - field: Records value: '11' - field: Distinct names value: '4' - field: Record types value: '9' - field: Shortest TTL value: '300' - field: Longest TTL value: '3600' - field: Unparsed lines value: '0' - field: Issues value: 0 errors, 1 warning records: - name: example.com. ttl: '3600' class: IN type: SOA value: >- ns1.example.com. hostmaster.example.com. 2026072601 7200 900 1209600 3600 - name: example.com. ttl: '3600' class: IN type: NS value: ns1.example.com. - name: example.com. ttl: '3600' class: IN type: NS value: ns2.example.com. - name: example.com. ttl: '3600' class: IN type: A value: 192.0.2.10 - name: example.com. ttl: '300' class: IN type: AAAA value: 2001:db8::10 - name: www.example.com. ttl: '3600' class: IN type: CNAME value: '@' - name: mail.example.com. ttl: '3600' class: IN type: A value: 192.0.2.20 - name: example.com. ttl: '3600' class: IN type: MX value: 10 mail - name: example.com. ttl: '3600' class: IN type: TXT value: '"v=spf1 ip4:192.0.2.20 -all"' - name: _sip._tcp.example.com. ttl: '3600' class: IN type: SRV value: 10 5 5060 sipserver.example.com. - name: example.com. ttl: '3600' class: IN type: CAA value: 0 issue "letsencrypt.org" typeCounts: - type: A count: '2' - type: NS count: '2' - type: AAAA count: '1' - type: CAA count: '1' - type: CNAME count: '1' - type: MX count: '1' - type: SOA count: '1' - type: SRV count: '1' - type: TXT count: '1' issues: - severity: Warning line: '17' detail: >- MX target "mail" has no trailing dot, so it resolves to mail.example.com. — add the dot if you meant an external name. normalized: "$ORIGIN example.com.\nexample.com.\t3600\tIN\tSOA\tns1.example.com. hostmaster.example.com. 2026072601 7200 900 1209600 3600\nexample.com.\t3600\tIN\tNS\tns1.example.com.\nexample.com.\t3600\tIN\tNS\tns2.example.com.\nexample.com.\t3600\tIN\tA\t192.0.2.10\nexample.com.\t300\tIN\tAAAA\t2001:db8::10\nwww.example.com.\t3600\tIN\tCNAME\t@\nmail.example.com.\t3600\tIN\tA\t192.0.2.20\nexample.com.\t3600\tIN\tMX\t10 mail\nexample.com.\t3600\tIN\tTXT\t\"v=spf1 ip4:192.0.2.20 -all\"\n_sip._tcp.example.com.\t3600\tIN\tSRV\t10 5 5060 sipserver.example.com.\nexample.com.\t3600\tIN\tCAA\t0 issue \"letsencrypt.org\"\n" json: |- { "origin": "example.com.", "directives": [ { "name": "$ORIGIN", "value": "example.com." }, { "name": "$TTL", "value": "3600" } ], "records": [ { "name": "example.com.", "ttl": 3600, "ttlSource": "directive", "class": "IN", "type": "SOA", "rdata": "ns1.example.com. hostmaster.example.com. 2026072601 7200 900 1209600 3600", "target": null, "line": 4 }, { "name": "example.com.", "ttl": 3600, "ttlSource": "directive", "class": "IN", "type": "NS", "rdata": "ns1.example.com.", "target": "ns1.example.com.", "line": 11 }, { "name": "example.com.", "ttl": 3600, "ttlSource": "directive", "class": "IN", "type": "NS", "rdata": "ns2.example.com.", "target": "ns2.example.com.", "line": 12 }, { "name": "example.com.", "ttl": 3600, "ttlSource": "directive", "class": "IN", "type": "A", "rdata": "192.0.2.10", "target": null, "line": 13 }, { "name": "example.com.", "ttl": 300, "ttlSource": "record", "class": "IN", "type": "AAAA", "rdata": "2001:db8::10", "target": null, "line": 14 }, { "name": "www.example.com.", "ttl": 3600, "ttlSource": "directive", "class": "IN", "type": "CNAME", "rdata": "@", "target": "example.com.", "line": 15 }, { "name": "mail.example.com.", "ttl": 3600, "ttlSource": "directive", "class": "IN", "type": "A", "rdata": "192.0.2.20", "target": null, "line": 16 }, { "name": "example.com.", "ttl": 3600, "ttlSource": "directive", "class": "IN", "type": "MX", "rdata": "10 mail", "target": "mail.example.com.", "line": 17 }, { "name": "example.com.", "ttl": 3600, "ttlSource": "directive", "class": "IN", "type": "TXT", "rdata": "\"v=spf1 ip4:192.0.2.20 -all\"", "target": null, "line": 18 }, { "name": "_sip._tcp.example.com.", "ttl": 3600, "ttlSource": "directive", "class": "IN", "type": "SRV", "rdata": "10 5 5060 sipserver.example.com.", "target": "sipserver.example.com.", "line": 19 }, { "name": "example.com.", "ttl": 3600, "ttlSource": "directive", "class": "IN", "type": "CAA", "rdata": "0 issue \"letsencrypt.org\"", "target": null, "line": 20 } ], "issues": [ { "severity": "Warning", "line": "17", "message": "MX target \"mail\" has no trailing dot, so it resolves to mail.example.com. — add the dot if you meant an external name." } ] } credits_used: 3 credits_remaining: null zone_with_mistakes_cname_conflict_duplicate_a: summary: Zone with mistakes (CNAME conflict, duplicate A) value: tool: dns-zone-file-parser tool_version: 1.0.1 outputs: summary: - field: Origin value: example.net. - field: Records value: '6' - field: Distinct names value: '3' - field: Record types value: '5' - field: Shortest TTL value: '300' - field: Longest TTL value: '300' - field: Unparsed lines value: '0' - field: Issues value: 1 error, 1 warning records: - name: example.net. ttl: '300' class: IN type: SOA value: >- ns1.example.net. admin.example.net. 1 7200 900 1209600 3600 - name: example.net. ttl: '300' class: IN type: NS value: ns1.example.net. - name: shop.example.net. ttl: '300' class: IN type: CNAME value: storefront.example.net. - name: shop.example.net. ttl: '300' class: IN type: TXT value: '"verification=abc123"' - name: blog.example.net. ttl: '300' class: IN type: A value: 198.51.100.5 - name: blog.example.net. ttl: '300' class: IN type: A value: 198.51.100.5 typeCounts: - type: A count: '2' - type: CNAME count: '1' - type: NS count: '1' - type: SOA count: '1' - type: TXT count: '1' issues: - severity: Error line: '6' detail: >- shop.example.net. has a CNAME alongside TXT — a CNAME must be the only record at its name. - severity: Warning line: '9' detail: >- Duplicate A for blog.example.net. (already on line 8). normalized: "$ORIGIN example.net.\nexample.net.\t300\tIN\tSOA\tns1.example.net. admin.example.net. 1 7200 900 1209600 3600\nexample.net.\t300\tIN\tNS\tns1.example.net.\nshop.example.net.\t300\tIN\tCNAME\tstorefront.example.net.\nshop.example.net.\t300\tIN\tTXT\t\"verification=abc123\"\nblog.example.net.\t300\tIN\tA\t198.51.100.5\nblog.example.net.\t300\tIN\tA\t198.51.100.5\n" json: |- { "origin": "example.net.", "directives": [ { "name": "$ORIGIN", "value": "example.net." }, { "name": "$TTL", "value": "300" } ], "records": [ { "name": "example.net.", "ttl": 300, "ttlSource": "directive", "class": "IN", "type": "SOA", "rdata": "ns1.example.net. admin.example.net. 1 7200 900 1209600 3600", "target": null, "line": 4 }, { "name": "example.net.", "ttl": 300, "ttlSource": "directive", "class": "IN", "type": "NS", "rdata": "ns1.example.net.", "target": "ns1.example.net.", "line": 5 }, { "name": "shop.example.net.", "ttl": 300, "ttlSource": "directive", "class": "IN", "type": "CNAME", "rdata": "storefront.example.net.", "target": "storefront.example.net.", "line": 6 }, { "name": "shop.example.net.", "ttl": 300, "ttlSource": "directive", "class": "IN", "type": "TXT", "rdata": "\"verification=abc123\"", "target": null, "line": 7 }, { "name": "blog.example.net.", "ttl": 300, "ttlSource": "directive", "class": "IN", "type": "A", "rdata": "198.51.100.5", "target": null, "line": 8 }, { "name": "blog.example.net.", "ttl": 300, "ttlSource": "directive", "class": "IN", "type": "A", "rdata": "198.51.100.5", "target": null, "line": 9 } ], "issues": [ { "severity": "Error", "line": "6", "message": "shop.example.net. has a CNAME alongside TXT — a CNAME must be the only record at its name." }, { "severity": "Warning", "line": "9", "message": "Duplicate A for blog.example.net. (already on line 8)." } ] } credits_used: 3 credits_remaining: null no_origin_or_ttl_filled_in_from_the_options: summary: No $ORIGIN or $TTL — filled in from the options value: tool: dns-zone-file-parser tool_version: 1.0.1 outputs: summary: - field: Origin value: example.org. - field: Records value: '3' - field: Distinct names value: '2' - field: Record types value: '3' - field: Shortest TTL value: 1h - field: Longest TTL value: 1h 30m - field: Unparsed lines value: '0' - field: Issues value: 0 errors, 1 warning records: - name: example.org. ttl: 1h class: IN type: SOA value: >- ns1.example.org. admin.example.org. 1 7200 900 1209600 3600 - name: example.org. ttl: 1h 30m class: IN type: NS value: ns1.example.org. - name: www.example.org. ttl: 1h 30m class: IN type: A value: 203.0.113.7 typeCounts: - type: A count: '1' - type: NS count: '1' - type: SOA count: '1' issues: - severity: Warning line: — detail: >- Records without a TTL and no $TTL directive — the Default TTL option was used instead. normalized: "$ORIGIN example.org.\nexample.org.\t3600\tIN\tSOA\tns1.example.org. admin.example.org. 1 7200 900 1209600 3600\nexample.org.\t5400\tIN\tNS\tns1.example.org.\nwww.example.org.\t5400\tIN\tA\t203.0.113.7\n" json: |- { "origin": "example.org.", "directives": [], "records": [ { "name": "example.org.", "ttl": 3600, "ttlSource": "record", "class": "IN", "type": "SOA", "rdata": "ns1.example.org. admin.example.org. 1 7200 900 1209600 3600", "target": null, "line": 1 }, { "name": "example.org.", "ttl": 5400, "ttlSource": "fallback", "class": "IN", "type": "NS", "rdata": "ns1.example.org.", "target": "ns1.example.org.", "line": 2 }, { "name": "www.example.org.", "ttl": 5400, "ttlSource": "fallback", "class": "IN", "type": "A", "rdata": "203.0.113.7", "target": null, "line": 3 } ], "issues": [ { "severity": "Warning", "line": "—", "message": "Records without a TTL and no $TTL directive — the Default TTL option was used instead." } ] } credits_used: 3 credits_remaining: null schema: type: object required: - tool - tool_version - outputs - credits_used - credits_remaining properties: outputs: type: object properties: summary: type: array description: Zone items: type: object properties: field: type: string description: Field value: type: string description: Value x-iotools-columns: - field - value records: type: array description: Records items: type: object properties: name: type: string description: Name ttl: type: string description: TTL class: type: string description: Class type: type: string description: Type value: type: string description: Value x-iotools-columns: - name - ttl - class - type - value typeCounts: type: array description: Record types items: type: object properties: type: type: string description: Type count: type: string description: Count x-iotools-columns: - type - count issues: type: array description: Issues items: type: object properties: severity: type: string description: Severity line: type: string description: Line detail: type: string description: Detail x-iotools-columns: - severity - line - detail normalized: type: string description: Normalised zone json: type: string description: JSON 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 ''.' 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_… ````