Automate obono RKSV

What obono RKSV is

Provides a RESTful API for interacting with virtual cash registers and creating receipts that are conform with the Registrierkassensicherheitsverordnung (RKSV). You may find our [automatically generated clients](./clients) for various programming languages and environments helpful...

What HumDay can do in obono RKSV

2 documented operations change something in obono RKSV.

• POSTGenerates an Abschlussbeleg./registrierkassen/{registrierkasseUuid}/abschluss
• PUTSigns a receipt and stores it in the "Datenerfassungsprotokoll"./registrierkassen/{registrierkasseUuid}/belege/{belegUuid}

What HumDay can read from obono RKSV

These are the operations a schedule or a trigger can watch.

• GETRequest a JWT access token using your obono username and password./auth
• GETGenerates a DEP file./registrierkassen/{registrierkasseUuid}/dep
• GETReturns a list of Monatsbelege./registrierkassen/{registrierkasseUuid}/monatsbelege
• GETRetrieves a particular Beleg from the "Datenerfassungsprotokoll"./belege/{belegUuid}
• GETReturns information about a particular Registrierkasse./registrierkassen/{registrierkasseUuid}
• GETRetrieves the Beleg collection from the "Datenerfassungsprotokoll"./registrierkassen/{registrierkasseUuid}/belege
• GETRetrieves a particular Beleg from the "Datenerfassungsprotokoll"./registrierkassen/{registrierkasseUuid}/belege/{belegUuid}
• GETRead belegUuid/export/qr/belege/{belegUuid}
• GETRead belegUuid/export/pdf/belege/{belegUuid}
• GETRead belegUuid/export/html/belege/{belegUuid}
• GETRead belegUuid/export/thermal-print/belege/{belegUuid}
• GETRead registrierkasseUuid/export/gobd/registrierkassen/{registrierkasseUuid}
• GETRead belege/export/csv/registrierkassen/{registrierkasseUuid}/belege
• GETRead belege/export/xls/registrierkassen/{registrierkasseUuid}/belege
• GETRead belege/export/dep7/registrierkassen/{registrierkasseUuid}/belege
• GETRead belege/export/dep131/registrierkassen/{registrierkasseUuid}/belege

How automating obono RKSV works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live obono RKSV account.
4. Grant access, then go live. You approve the specific obono RKSV operations it may use — and only those.

Automate obono RKSV with these

• Magento B2B455 operations
• Klaviyo345 operations
• Agco ATS AGCO277 operations
• BeezUP Merchant210 operations
• Rebilly184 operations
• reverb163 operations
• Jumpseller142 operations
• Swagger API2Cart141 operations
• Just Eat UK97 operations
• Billbee75 operations
• Velopayments Velo Payments75 operations
• Apigee Marketcheck71 operations

Categories

• E-commerce

Questions about obono RKSV automation

Can HumDay connect to obono RKSV?

Yes. HumDay reads obono RKSV's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 18 operations are documented.

Do I need to write code to automate obono RKSV?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your obono RKSV account.

What can HumDay do in obono RKSV?

2 of the 18 documented operations change something in obono RKSV, and 16 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my obono RKSV account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to obono RKSV is held behind that approval.

Where this came from

The operations above are read from a published API description for obono RKSV at app.obono.at/api/docs/api.yml. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.