Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request - API #251

Closed
bastilimbach opened this issue Jul 31, 2018 · 9 comments
Closed

Feature request - API #251

bastilimbach opened this issue Jul 31, 2018 · 9 comments

Comments

@bastilimbach
Copy link

Kimai v2 looks awesome! Congratulation! Really looking forward to the future of v2.

Are there any plans to implement an API to create timesheet entries, manage users etc...?

Proposed API v1:
GET timesheet: Get timesheet (all records) of user xyz
POST timesheet: Create a new record in the timesheet for user xyz
GET timesheet/recordID: Get record xyz of user xyz
PUT timesheet/recordID: Update record in the timesheet for user xyz
DELETE timesheet/recordID: Delete record in the timesheet for user xyz

API v2:
GET users: Get all users
POST users: Create a new users
GET users/userID: Get user with id xyz
PUT users/userID: Update user with id xyz
DELETE users/userID: Delete user with id xyz

CRUD operations for projects
CRUD operations for customers
CRUD operations for activities

API v3:
Invoice management: API to create invoices.

@kevinpapst
Copy link
Member

Yes, plans are there but so much other stuff to do as well first ;-)
But its good that we now have it as official Feature request.

@kevinpapst
Copy link
Member

Actually I had to start on working on a basic API while working on global activities.
This API will be read-only for now, but you are welcome to have a look and add your ideas!

@bastilimbach
Copy link
Author

bastilimbach commented Aug 6, 2018

I would love to contribute! I just need to read myself into Symphony 4.

@kevinpapst
Copy link
Member

Great! I try to push all the changes required for the basic setup today/tomorrow.

@kevinpapst
Copy link
Member

You know that the first basic API is in place? It supports reading only, but its there.

@kevinpapst
Copy link
Member

kevinpapst commented Sep 7, 2018

Its hard to handle bulk tickets like this one, with multiple feature requests in one - they tend not to get closed ever ;-)
To prevent that, I will close this ticket as a basic read API + documentation is in place now.

Could you please open new PRs for every endpoint you need.
Probably really when you need it and not in advance.

Thanks for supporting Kimai @bastilimbach 👍

@bastilimbach
Copy link
Author

@kevinpapst I'm already testing the current read-only API. To be honest with you, I didn't think that you would be so fast at implementing this. 👍

As soon as I implement the read-only API inside Timeu, I try to add the basic "Create Entry" API as a PR.

@kevinpapst
Copy link
Member

I think an App would really push Kimai 2 forward - so I will help you as good and fast as I can:
Don't be shy, open as many new PRs as you like!

Just let me know if you need any filter/search/endpoint ... in the API, its a bit hard to build it without a real-usecase ;-)

@lock
Copy link

lock bot commented Nov 18, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Nov 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants