The contact ID shown in these code examples is fictitious and won't work in your app. In your app, you'll need use a valid contact ID. Here are some examples of ways to get contact IDs to use in the path parameter:
Use the contact ID of a contact.
Get info about the currently signed-in user's contacts and friends by specifying me as the user ID, as in:
me/contacts, to get info about all of the signed-in user's contacts.
me/friends, to get info about all of the signed-in user's friends.
Note A friend is another Outlook.com user that a user has invited to be a friend and that has accepted the friend request. A friend is a contact that has its is_friend structure set to true. (You can't set theis_friend structure programmatically.)
If you have the user ID of someone, get info about his or her contacts and friends by using the user ID in place of USER_ID as shown in these examples:
USER_ID/contacts, to get info about all of the contact entries for the user represented by USER_ID.
USER_ID/friends, to get info about all of the friend entries for the user represented by USER_ID.
You can also use the contact ID argument to filter the results returned in a collection. For example:
Get a limited number of contact or friend entries by using the limit parameter in the preceding code to specify the number of entries to get. For example, to get the first two contact entries for the signed-in user, use me/contacts?limit=2.
Specify the first contact or friend entry to get by setting the offset parameter in the preceding code to the index of the first entry that you want to get. For example, to get two contact entries for the signed-in user, starting at the third contact entry, use me/contacts?limit=2&offset=3.
Note In the JavaScript Object Notation (JSON)-formatted object that's returned, you can look in the paging object for the previous and next structures to get the offset and limit parameter values of the previous and next entries.