1
Completed

API could support multiple IDs per http send request.

In the current API, If I have to send out 100 notifications, it would take more than 50 seconds if I were to be nice to your API.

I propose I could rather submit a list of users (i.e. a comma seperated string of users), for up to, say 10 users. Sending the notifications would take 5 seconds instead and produce less stress on your web servers.

Ps. I am unable to use the Group functionality for my use case, as the recipient groups are dynamic on each "run".

Follow

1 reply

Votes Newest Oldest

Our API already supports sending to multiple user keys in one request, up to 50 user keys separated by commas.

https://pushover.net/api#identifiers

Additionally, you can always send as many API requests as you want, as quickly as you can as long as it's over a single HTTP connection, or multiple connections in sequence (not in parallel).  The "being friendly" guide only warns against making multiple simultaneous connections, and if you issue a bad request (resulting in a 4xx response), you need to slow down.

Topic is closed for comments