> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/developers/api-documentation/printer/send-print-job-to-printer-required-permissions-printer.md). Send print job to printer\ \ Required permissions: PRINTER ============================= Sends print data straight to the printer, exactly as you supply it. Flow applies no rendering and no formatting, so the data has to be in the language the printer speaks: ESC/POS for a receipt printer, ZPL for a label printer, PDF for a general printer. Send the data either as a binary body with content type application/octet-stream, or base64 encoded in a JSON body with content type application/json. The two are equivalent. A 202 means the printer accepted the job. A 502 means the printer, or the connection to it, reported an error - the message field carries what it reported. For a CloudPRNT printer, 202 means the job is queued; the printer fetches it on its next poll. Look up the result with GET .../jobs/{printJobUid}. ```json {"openapi":"3.0.2","info":{"title":"Flow Retail API version 2","version":"2.0.0"},"tags":[{"name":"Printer","description":"Printer"}],"servers":[{"description":"Flow Retail Production","url":"https://api.flowretail.com/v2"},{"description":"Flow Retail Stage","url":"https://api.stage.flowretail.com/v2"}],"security":[{"accessToken":[]},{"authToken":[]},{"integrationToken":[]}],"components":{"securitySchemes":{"accessToken":{"description":"Access token recevied after user login with a deviceToken","scheme":"bearer","type":"http"},"authToken":{"description":"Token received from the auth service","scheme":"bearer","type":"http"},"integrationToken":{"scheme":"bearer","type":"http"}},"requestBodies":{"PrintJobRequest":{"content":{"application/octet-stream":{"schema":{"type":"string","format":"binary"}},"application/json":{"schema":{"$ref":"#/components/schemas/PrintJobRequestSchema"}}},"required":true}},"schemas":{"PrintJobRequestSchema":{"title":"PrintJobRequestSchema","type":"object","description":"Print data for a print job, base64 encoded. Use this when you send the\njob as application/json; send the bytes themselves if you use\napplication/octet-stream instead.\n","properties":{"base64Data":{"type":"string","description":"base64 encoded print data, passed to the printer as-is"}},"required":["base64Data"]},"PrintJobAcceptedResponseSchema":{"title":"PrintJobAcceptedResponseSchema","type":"object","properties":{"printJobUid":{"type":"string","description":"Set when the printer fetches its jobs itself (CloudPRNT). Look the job up with GET .../jobs/{printJobUid}."}}}},"responses":{"GenericErrorResponse":{"content":{"application/json":{"schema":{"properties":{"code":{"type":"string","description":"Error code. The codes a POS app acts on are listed in DeviceErrorCodeENUM."},"message":{"type":"string","description":"Error message in the locale you specify in the Accept-Language header or specified on the user"},"logId":{"type":"string","description":"Log identification. Can be used when reporting errors to Flow Solutions"}},"type":"object"}}},"description":"Linking failed. Ther error message will have information about what failed."}}},"paths":{"/tenants/{tenantUid}/printers/{printerUid}/jobs":{"post":{"summary":"Send print job to printer\n\nRequired permissions: PRINTER","tags":["Printer"],"operationId":"post-tenants-tenantUid-printers-printerUid-jobs","description":"Sends print data straight to the printer, exactly as you supply it.\nFlow applies no rendering and no formatting, so the data has to be\nin the language the printer speaks: ESC/POS for a receipt printer,\nZPL for a label printer, PDF for a general printer.\n\nSend the data either as a binary body with content type\napplication/octet-stream, or base64 encoded in a JSON body with\ncontent type application/json. The two are equivalent.\n\nA 202 means the printer accepted the job. A 502 means the printer,\nor the connection to it, reported an error - the message field\ncarries what it reported.\n\nFor a CloudPRNT printer, 202 means the job is queued; the printer\nfetches it on its next poll. Look up the result with\nGET .../jobs/{printJobUid}.\n","requestBody":{"$ref":"#/components/requestBodies/PrintJobRequest"},"responses":{"202":{"description":"Print job accepted. For a CloudPRNT printer it is queued, and printJobUid is set.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/PrintJobAcceptedResponseSchema"}}}},"400":{"$ref":"#/components/responses/GenericErrorResponse"},"404":{"$ref":"#/components/responses/GenericErrorResponse"},"413":{"$ref":"#/components/responses/GenericErrorResponse"},"502":{"$ref":"#/components/responses/GenericErrorResponse"}}}}}} ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flowretail.com/docs/developers/api-documentation/printer/send-print-job-to-printer-required-permissions-printer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.