Carriers the account can print labels with

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://api.documentation.omnicado.com/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json
{
  "omnicado MCP server": {
    "url": "https://api.documentation.omnicado.com/mcp"
  }
}

Close
GET /labels/carriers

Carriers installed on the account (for a colleague's token, on the manager's account). customLabels says whether the carrier can print with POST /labels/custom. labelFormats lists the formats you can request; when it is empty, the carrier prints in the format set in its installation (for example the GLS printer type) and ignores the one you ask for.

Responses

  • 200 application/json

    Installed carriers

    Hide response attributes Show response attributes object
    • data array[object]
      Hide data attributes Show data attributes object
      • code string

        Values are dpd, dpdSk, gls, oneByAllegro, packeta, ppl, sps, toptrans, or wedo.

      • name string
      • orderLabels boolean

        Can print labels for orders

      • customLabels boolean

        Can print with POST /labels/custom

      • labelFormats array[string]

        Formats you can request. Empty when the carrier prints in the format set in its installation.

        Values are pdf or zpl.

    • defaultLabelFormat string

      The account's label format, used when a request does not name one

      Values are pdf or zpl.

  • 401

    Missing or invalid API token

GET /labels/carriers
curl \
 --request GET 'api.services.omnicado.com/api/v2/labels/carriers' \
 --header "X-OMNICADO-TOKEN: $API_KEY"
Response examples (200)
{
  "data": [
    {
      "code": "packeta",
      "name": "Packeta",
      "orderLabels": true,
      "customLabels": true,
      "labelFormats": [
        "pdf",
        "zpl"
      ]
    }
  ],
  "defaultLabelFormat": "pdf"
}