# New Python API published **URL:** \ **Category:** Developing for Dolibarr\ **Tags:** API\ **Created:** [February 5, 2025, 9:56pm UTC](https://www.dolibarr.org/forum/t/new-python-api-published/29933 "2025-02-05T21:56:41Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![egils](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/e/a88e57/32.png) [@egils](https://www.dolibarr.org/forum/u/egils)\ **Post date:** [February 5, 2025, 9:56pm UTC](https://www.dolibarr.org/forum/t/new-python-api-published/29933/1 "2025-02-05T21:56:42Z")
I decided to publish my Python API [GitHub - dpriskorn/dolibarr\_python\_api\_public: Extensive Dolibarr API written in Python.](https://github.com/dpriskorn/dolibarr_python_api_public/) It’s 12k lines and tested with v14. It supports a lot of endpoints. 🙂 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? ---
**Author:** ![jonbendtsen](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jonbendtsen](https://www.dolibarr.org/forum/u/jonbendtsen)\ **Post date:** [February 6, 2025, 6:45am UTC](https://www.dolibarr.org/forum/t/new-python-api-published/29933/2 "2025-02-06T06:45:53Z")
> [@egils](#): > > GitHub - dpriskorn/dolibarr\_python\_api\_public: Extensive Dolibarr API written in Python. wooow, seems like good work 🙂 Why did you only test it with v14? ---
**Author:** ![jonbendtsen](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jonbendtsen](https://www.dolibarr.org/forum/u/jonbendtsen)\ **Post date:** [February 6, 2025, 6:46am UTC](https://www.dolibarr.org/forum/t/new-python-api-published/29933/3 "2025-02-06T06:46:38Z")
I am not seeing any license? ---
**Author:** ![jonbendtsen](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jonbendtsen](https://www.dolibarr.org/forum/u/jonbendtsen)\ **Post date:** [February 6, 2025, 4:40pm UTC](https://www.dolibarr.org/forum/t/new-python-api-published/29933/4 "2025-02-06T16:40:13Z")
I would prefer either BSD/MIT and/or the same license as Dolibarr is in ---
**Author:** ![egils](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/e/a88e57/32.png) [@egils](https://www.dolibarr.org/forum/u/egils)\ **Post date:** [February 7, 2025, 9:08am UTC](https://www.dolibarr.org/forum/t/new-python-api-published/29933/5 "2025-02-07T09:08:28Z")
In enterprise upgrading must be carefully considered. Benefits vs risks. I have not found any good reasons to upgrade fom v14 yet 🤷‍♂️ You are very welcome to test it against newer versions. 😀 I included supplier specific code which should probably be moved to an example folder because it is useless for most people. ---
**Author:** ![jonbendtsen](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jonbendtsen](https://www.dolibarr.org/forum/u/jonbendtsen)\ **Post date:** [March 26, 2025, 5:41pm UTC](https://www.dolibarr.org/forum/t/new-python-api-published/29933/6 "2025-03-26T17:41:55Z")
Thank you for deciding on a GPLv3 license 🙂 So far I’ve forked it, and since I like Python and Dolibarr, I hope I’ll take a much more detailed look 🙂 > ---
**Author:** ![quastech](https://www.dolibarr.org/forum/user_avatar/www.dolibarr.org/quastech/32/9138_2.png) [@quastech](https://www.dolibarr.org/forum/u/quastech)\ **Post date:** [March 21, 2026, 9:46am UTC](https://www.dolibarr.org/forum/t/new-python-api-published/29933/7 "2026-03-21T09:46:01Z")
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! ---
**Author:** ![jonbendtsen](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jonbendtsen](https://www.dolibarr.org/forum/u/jonbendtsen)\ **Post date:** [March 21, 2026, 10:26pm UTC](https://www.dolibarr.org/forum/t/new-python-api-published/29933/8 "2026-03-21T22:26:48Z")
> [@quastech](#): > > 1. Naming: > You can consider something like: > > - DolibarrPy > - PyDolibarr API > - Dolibarr Python SDK Sorry, DolibarrPy is already taken > **[Client Challenge](https://pypi.org/project/dolibarrpy/)** ---
**Author:** ![zachmelo](https://www.dolibarr.org/forum/user_avatar/www.dolibarr.org/zachmelo/32/9195_2.png) [@zachmelo](https://www.dolibarr.org/forum/u/zachmelo)\ **Post date:** [April 2, 2026, 5:42pm UTC](https://www.dolibarr.org/forum/t/new-python-api-published/29933/9 "2026-04-02T17:42:06Z")
Interesting! I’ve had some good luck using the standard REST API with python tools. Great work!