Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
openapi: 3.2.0
info:
title: Labelixa Com Diagnostics API
version: 0.4.0
description: 'Operations tagged Diagnostics across 2 of this provider''s published API definitions: labelixa-com-api-openapi.json, labelixa-com-openapi.json. Each path carries the servers of the definition it was published in.'
tags:
- name: Diagnostics
paths:
/v1/diagnostics:
post:
summary: Lint ZPL
description: 'Analyses ZPL without rendering it and returns findings with line and column, a summary, field origins (`alanlar`) and RFID blocks. Optional label context `?dpmm=&w=&h=`; `?model=` adds the compatibility findings for that printer model (unknown models return 400 with the list). Every finding carries the address of its rule page. Uses the same identity as rendering but does not count against the operation quota; only the per-second rate limit (shared with rendering) applies. Stateless: the ZPL is not stored or logged. The response never echoes the submitted code back. 413 for bodies over 1 MB.'
operationId: diagnostics_v1_diagnostics_post
parameters:
- name: dpmm
in: query
required: false
schema:
type: integer
default: 8
title: Dpmm
- name: w
in: query
required: false
schema:
type: number
default: 4.0
title: W
- name: h
in: query
required: false
schema:
type: number
default: 6.0
title: H
- name: model
in: query
required: false
schema:
type: string
default: ''
title: Model
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Diagnostics
/v1/diagnostics/full:
post:
summary: Full ZPL health report
description: 'Same contract as `/v1/diagnostics` (stateless, no quota, rate limit only, no echo of the code) but the answer is sectioned: rule findings, size/DPI analysis, and memory and `^PQ` summaries in one report. The score covers only the sections that could be evaluated; a section that could not be measured says so.'
operationId: diagnostics_full_v1_diagnostics_full_post
parameters:
- name: dpmm
in: query
required: false
schema:
type: integer
default: 8
title: Dpmm
- name: w
in: query
required: false
schema:
type: number
default: 4.0
title: W
- name: h
in: query
required: false
schema:
type: number
default: 6.0
title: H
- name: model
in: query
required: false
schema:
type: string
default: ''
title: Model
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Diagnostics
components:
schemas:
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError
x-refined-from:
- labelixa-com-api-openapi.json
- labelixa-com-openapi.json