contacts.json

{
  "_links": {
    "self": "/contacts"
  },
  "_embedded": {
    "contact": [{
      "_links": {
        "self": { "href": "/contacts/1" }
      },
      "name": "Bob Marley",
      "telephone": "123-456-7890",
      "email": "name@example.com",
      "birthdate": "01/11/1990",
      "address": "123 Jersey St, New York, NY 10001"
    },
    {
      "_links": {
        "self": { "href": "/contacts/2" }
      },
      "name": "John Smith",
      "telephone": "123-456-7890",
      "email": "name@example.com",
      "birthdate": "02/20/1980",
      "address": "123 Jersey St, New York, NY 10001"
    }] 
  }
}

GET /contacts returns the list.
POST /contacts with a payload of a contact/person JSON (with name, telephone, etc) will create a contact.
GET /contacts/id returns the contact
POST /contacts/id updates the contact based on the contact/person JSON payload.
DELETE /contacts/id removes the specified contact.

Note that I think we might add authentication on specific deletes later. We can talk about this. E.g., trying to edit or delete /contacts/1 works fine, but /contacts/2 requires authentication. Just something to consider. It shows that the authentication is reactive (stateless).