New Python API published

I decided to publish my Python API GitHub - dpriskorn/dolibarr_python_api_public: Extensive Dolibarr API written in Python.
It’s 12k lines and tested with v14.
It supports a lot of endpoints. :slight_smile:

I have not decided which license to release it under, what do you prefer?
Maybe giving it a better name would be a good idea, any suggestions?

2 Likes

wooow, seems like good work :slight_smile:

Why did you only test it with v14?

I am not seeing any license?

I would prefer either BSD/MIT and/or the same license as Dolibarr is in

1 Like

In enterprise upgrading must be carefully considered.
Benefits vs risks. I have not found any good reasons to upgrade fom v14 yet :man_shrugging:
You are very welcome to test it against newer versions. :grinning:

I included supplier specific code which should probably be moved to an example folder because it is useless for most people.

Thank you for deciding on a GPLv3 license :slight_smile:

So far I’ve forked it, and since I like Python and Dolibarr, I hope I’ll take a much more detailed look :slight_smile:

Hi,

This looks really interesting—great work on building a Python API for Dolibarr

Regarding your questions:

  1. Testing only on v14:
    You may want to test on v15+ as well since API endpoints and authentication handling have evolved in newer versions. It will improve compatibility and adoption.

  2. License suggestion:
    MIT or Apache 2.0 would be good choices if you want wider adoption and flexibility.

  3. Naming:
    You can consider something like:

  • DolibarrPy
  • PyDolibarr API
  • Dolibarr Python SDK

Also, adding proper documentation and examples (especially for authentication and CRUD operations) will help developers a lot.

I’ve worked with Python integrations in ERP environments and seen similar use cases while training learners, so this could be very useful for beginners as well.

Great work again!

Sorry, DolibarrPy is already taken