Correct type of URL for end point'a?

Question

API

Suppose there is an entity "Event", which includes 4 fields: title, date, location, owner. How to "correctly" organize the URL if you need to update this structure:
1. /event/update/ and in json we pass the field name and value, for example: {"title" : "Great event", "owner" : "Karl" } .
Or put the field value in the url itself, and the value as a parameter:
2. /event/update/title/:param

Answer 1

1st. Even better
GET /events - list of events with filter
GET /events/:id - data of one selected event
POST /events - create new
PUT /events/:id - update event
DELERE /events/:id - delete event