Rest API Best Practice - Single action and Bulk - rest

Question

Let my server have the ability to perform an action called 'A'.
Now, My server needs to have an extra ability to perform bulk 'A' actions.
The route on the server is:
/entity/:entityId/'A'/:'A'Id
Adding the bulk ability faced me with two approaches:
1) Exposing 2 routes to each method:
/entity/:entityId/'A'/:'A'Id and
/entity/:entityId/'A' with a list of 'A' ids in the request's body.
2) Drop the 'A'Id paramater and add a query parameter to the first route called bulk with boolean value:
/entity/:entityId/'A'/?bulk=boolean
And if bulk == true look for 'A'Id[] at the request's body.
else if bulk == false look for id entry at the request's body.
I'm feeling that the 1st approach is better, I'd love to hear thoughts, or maybe a very different approach.
Any opinion is blessed to hear,
Thanks.

Answer 1

Query params are good for GET methods like:
curl -X GET host.com/megacorp/employee?employee_id[]=1&employee_id[]=2
But for POST and PUT methods it's better to use something like this:
curl -XPOST host.com/megacorp/employee/_bulk -d '{"data":[
{"id":"1", "name": "John Doe"},
{"id":"2", "name": "Jane Doe"}
]}'
And to POST or PUT 1 resource - simply provide 1 object in request, like:
curl -XPUT host.com/megacorp/employee/1 -d '{
"name": "JOHN DOE"
},'