Skip to content
Components

mPOHODA

Create invoices, orders, offers, business partners and other records in the mPOHODA cloud accounting API from Keboola tables, with a results table per run.

mPOHODA is STORMWARE’s cloud accounting service. The mPOHODA data destination connector creates records in it from Keboola tables through the REST API. One configuration row writes to one agenda: business partners, issued invoices, issued advance invoices, received invoices, issued orders, received orders, issued offers, issue slips, other liabilities or payment methods. The mPOHODA data source connector reads the agendas the other way.

Each record’s outcome, whether success with the assigned document number or a validation error, is written to a write_results table. Validation errors (HTTP 422) are recorded per record; the run fails only if every record fails.

  • The mPOHODA Pro edition. Other editions have no API.
  • An API key, generated in mPOHODA under Nastavení → Open API. The key is bound to one company.

The official API documentation is at api.mpohoda.cz/doc.

Create a new configuration of the mPOHODA data destination connector.

FieldDescription
API base URLhttps://api.mpohoda.cz/v1 for the Czech mPOHODA, https://api.mpohoda.sk/v1 for the Slovak one.
API keyYour mPOHODA API key. The value is stored encrypted.
Request timeout (s)Timeout of one API request. Default 60.

Click Test connection to verify the key and the base URL, then save.

Screenshot - mPOHODA connection settings

Click Add Row and configure one row per agenda.

FieldDescription
AgendaThe resource to create records in.
Input modeColumn mapping (default) maps input columns to mPOHODA fields. Raw JSON posts one input column verbatim as the full request body.
FieldDescription
Header tableOptional. Input table with one row per record, the document header for document agendas. Auto-detected when left empty.
Line items tableOptional. Input table with the line items of a document agenda, linked to the header by the key column. Auto-detected when left empty, and ignored for agendas without line items, such as business partners and payment methods.
Document key columnColumn present in both the header and line-items tables that links items to their document. Required when the line items table is set explicitly.
Column mappingMaps input columns to mPOHODA fields. Click Load columns to prefill it, and leave it empty if your columns already use the mPOHODA field names. For line items, include an item_type column with the value price_list or text; it selects the line variant.

Screenshot - mPOHODA row in column mapping mode

FieldDescription
JSON body columnThe input column holding the full mPOHODA request body, one JSON object per row. Default body.

Use raw JSON for fields the column mapping does not expose.

The write_results table has one row per input record: the row, agenda, status, mPOHODA id, the assigned document number and a message.

Ask Kai

Hi, I'm Kai — Keboola's AI assistant for the docs. Ask me anything and I'll answer from the documentation and cite the pages I use.

Kai is an AI and can make mistakes. Check the sources it links.