-
Notifications
You must be signed in to change notification settings - Fork 31
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
Posting multiple tasks with one request #17
Comments
This would also be useful for other endpoints such as time entries, since as far as I know, there is no bulk import mechanism when migrating from a different service to Paymo. Even if it would be limited to 100 or 10 objects, it still would mean a big performance improvement, for the client and probably also for the server. |
This request appears to be about 8 years old and there is still no way to POST (Create) multiple objects or an array of objects, at least that I could find. Considering how long this request has been open, is Paymo intentionally blocking the ability to perform bulk imports, or is that just a feature request that has not been prioritized yet? |
UPDATEISSUE: Rate LimitI was able to successfully submit multiple POST Time Entry Create requests via Postman (see below). Unfortunately, I ran into the next Paymo BLOCKER... the Paymo API only allows (5) POST requests before responding with "Too Many Requests". Paymo seems like they really do not want people to migrate into their system. They seem to put up barrier after blocker after barrier. Following is the method for POST creating up to (5) time entries. SOLVED: Rate LimitBased on Paymo API Docs > Rate Limiting (https://github.com/paymoapp/api?tab=readme-ov-file#rate-limiting).
The method below has been updated to include this. Postman Multiple POST Request Method
|
I suggest adding a way to create multiple tasks in one request. I'm working in a project that loads projects to paymo and I have to create many tasks at once. This is not good either for you or me, I have to make a lot of calls sequentially and I'm pretty sure your server is not happy about it.
The text was updated successfully, but these errors were encountered: