# API I development?

**URL:** <https://community.dlubal.com/t/api-i-development/5714>\
**Category:** API & Interfaces\
**Tags:** dlubal-api, api-2\
**Created:** [November 14, 2026, 3:32pm UTC](https://community.dlubal.com/t/api-i-development/5714 "2026-11-14T15:32:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mejra](https://community.dlubal.com/letter_avatar_proxy/v4/letter/m/958977/32.png) [@mejra](https://community.dlubal.com/u/mejra)\
**Post date:** [November 14, 2026, 3:32pm UTC](https://community.dlubal.com/t/api-i-development/5714/1 "2026-11-14T15:32:54Z")

</div>

As far as I understand, Dlubal has officially discontinued the development of API I, and according to recent statements on this forum, it will no longer be maintained either.

So, just to clarify: are we now in a situation where the only actively developed API is the one with usage-based credit limits, meaning that customers who want to continue developing their own automation tools are effectively being pushed towards additional recurring costs?

I have spent the past year developing scripts using API II to automate my RFEM workflows and exchange data with CAD. With the current API credit limits, I can barely do something as simple as exporting a table.

And yes, I know I can buy more credits. But I already pay for a service package, and I am not particularly interested in paying Dlubal even more money just to use scripts I wrote myself.

The sad part is that I used to be a huge Dlubal fan. I have attended your conferences, talked to Mr. Brož several times, and always thought Dlubal was a company that genuinely understood engineers. I suppose I was naive to think that the trend of squeezing additional revenue out of existing customers would never reach Dlubal.

Actually, I have a great idea for your business team: **why not start charging us for clicking the "Calculate" button next?** Anyone who wants to run more than 10 calculations per month would simply need to purchase an additional subscription. Think of all that untapped revenue!

---

<div class="post-metadata">

**Author:** ![Pier53](https://community.dlubal.com/letter_avatar_proxy/v4/letter/p/4bbf92/32.png) [@Pier53](https://community.dlubal.com/u/Pier53)\
**Post date:** [November 14, 2026, 8:22pm UTC](https://community.dlubal.com/t/api-i-development/5714/2 "2026-11-14T20:22:07Z")

</div>

"I'm also confused about the Dlubal API. I initially assumed it was cloud-based (and therefore expensive), but apparently not: it still requires my computer to be running, along with my licence, the software, my graphics card, etc.

I also still don't understand how it differs from running a Python script directly inside RFEM. That option seems 'free' (as long as you have a licence) and works basically the same way as the API, yet supposedly they don't offer exactly the same capabilities. It's quite confusing.

Out of curiosity, what kind of scripts and workflow did you set up? Concrete or steel analysis? I'd love to hear more about it."