Specifies information about an event, including the location, event name, and which invitees plan to attend. The User, Page, and Application objects have an events connection.
To read an Event, you need one of the following:
Starting July 5th, an access token will be required to access even public events. To read an Event, you will need one of the following:
To read the /events connection of a User, you need:
user_events permission for the current userfriends_events permission for a friend of the current userThe Facebook Developer Garage Austin Event:
https://graph.facebook.com/331218348435
| Name | Description | Permissions | Returns |
id | The event ID | generic |
|
owner | The profile that created the event | generic | object containing |
name | The event title | generic |
|
description | The long-form description of the event | generic |
|
start_time | The start time of the event, as you want it to be displayed on facebook | generic |
|
end_time | The end time of the event, as you want it to be displayed on facebook | generic |
|
location | The location for this event | generic |
|
venue | The location of this event | generic | object containing one or more of the following fields: |
privacy | The visibility of this event | generic |
|
updated_time | The last time the event was updated | generic |
|
| Name | Description | Permissions | Returns |
| feed | This event's wall. | any valid | An array of |
| noreply | All of the users who have been not yet responded to their invitation to this event. | any valid |
|
| invited | All of the users who have been invited to this event. | any valid |
|
| attending | All of the users who are attending this event. | any valid |
|
| maybe | All of the users who have been responded "Maybe" to their invitation to this event. | any valid |
|
| declined | All of the users who declined their invitation to this event. | any valid |
|
| picture | The event's profile picture. | any valid | Returns a HTTP 302 with the URL of the event's picture (use ?type=small | normal | large to request a different photo). |
| videos | The videos uploaded to an event. | valid user |
|
This connection corresponds to the Event's wall. You can create a link, post or status message by issuing an HTTP POST request to the EVENT_ID/feed connection.
You can post a link on the event's wall by issuing an HTTP POST request to EVENT_ID/feed with the publish_stream permissions and the following parameters.
| Parameter | Description | Type | Required |
|---|---|---|---|
link |
Link URL | string |
yes |
message |
Link message | string |
no |
The other fields are taken from the metadata of the page URL given in the 'link' param.
If the create is successful, you get the following return.
| Name | Description | Type |
|---|---|---|
id |
The new link ID | string |
You can create a post on an Event's wall by issuing an HTTP POST request to EVENT_ID/feed with the publish_stream permissions and the following parameters.
| Parameter | Description | Type | Required |
|---|---|---|---|
message |
Post message | string |
either message or link |
link |
Post URL | string |
either message or link |
picture |
Post thumbnail image (can only be used if link is specified) |
string |
no |
name |
Post name (can only be used if link is specified) |
string |
no |
caption |
Post caption (can only be used if link is specified) |
string |
no |
description |
Post description (can only be used if link is specified) |
string |
no |
actions |
Post actions | array of objects containing name and link |
no |
If the create is successful, you get the following return.
| Name | Description | Type |
|---|---|---|
id |
The new post ID | string |
You can post a status message on an Event's wall by issuing an HTTP POST request to EVENT_ID/feed with the publish_stream permissions and the following parameters.
| Parameter | Description | Type | Required |
|---|---|---|---|
message |
Status Message content | string |
yes |
If the create is successful, you get the following return.
| Name | Description | Type |
|---|---|---|
id |
The new status message ID | string |
You can invite users to an event by issuing an HTTP POST to /EVENT_ID/invited/USER_ID. You can invite multiple users by issuing an HTTP POST to /EVENT_ID/invited?users=USER_ID1,USER_ID2,USER_ID3. Both of these require the create_event permission and return true if the invite is successful.
You can read the list of invitees for an event by issuing an HTTP GET to /EVENT_ID/invited:
https://graph.facebook.com/331218348435/invited
You can check whether a specific user has been invited to an event by issuing an HTTP GET to /EVENT_ID/invited/USER_ID:
https://graph.facebook.com/331218348435/invited/2503747
You'll need the user_events or friend_events permissions to view the invite list for for non-public events.
These calls return an object with the name, id, and rsvp_status ('not_replied', 'unsure', 'attending', or 'declined') fields. When checking for a specific user, if the user is not invited to the event, the API will return an empty data array.
You can un-invite a user from an event by issuing an HTTP DELETE to /EVENT_ID/invited/USER_ID. Returns true if the request is successful. The user must be an admin (i.e. creator) of the event for this call to succeed. Requires rsvp_event permission.
You can RSVP the user as 'attending' an Event by issuing an HTTP POST to EVENT_ID/attending. This requires the rsvp_event permission and returns true if the RSVP is successful, and false otherwise.
You can which users are 'attending' an event by issuing an HTTP GET to /EVENT_ID/attending This returns a list of all users who responded 'yes' to the event:
https://graph.facebook.com/331218348435/attending
You can check if a specific user responded 'yes' to an event by issuing an HTTP GET to /EVENT_ID/attending/USER_ID. These operations require the user_events or friends_events permissions for non-public events and return an array of objects with the name, id, and rsvp_status fields. When checking a single user, an empty data will be returned if the user did not respond 'yes' to the event.
You can RSVP the user as a 'maybe' for an Event by issuing an HTTP POST to EVENT_ID/maybe. This requires the rsvp_event permission and returns true if the RSVP is successful, and false otherwise.
You can which users have replied 'maybe' to an event by issuing an HTTP GET to /EVENT_ID/maybe This returns a list of all users who responded 'maybe' to the event:
https://graph.facebook.com/331218348435/maybe
You can check if a specific user responded 'maybe' to an event by issuing an HTTP GET to /EVENT_ID/maybe/USER_ID. These operations require the user_events or friends_events permissions for non-public events and return an array of objects with the name, id, and rsvp_status fields. When checking a single user, an empty data will be returned if the user did not respond 'maybe' to the event.
You can RSVP the user as 'declined' for an Event by issuing an HTTP POST to EVENT_ID/declined. This requires the rsvp_event permission and returns true if the RSVP is successful, and false otherwise.
You can which users are declined an event (i.e. responded 'no') by issuing an HTTP GET to /EVENT_ID/declined This returns a list of all users who responded 'no' to the event:
https://graph.facebook.com/331218348435/declined
You can check if a specific user responded 'no' to an event by issuing an HTTP GET to /EVENT_ID/declined/USER_ID. These operations require the user_events or friends_events permissions for non-public events and return an array of objects with the name, id, and rsvp_status fields. When checking a single user, an empty data will be returned if the user did not respond 'no' to the event.
You can which users have not replied to an event by issuing an HTTP GET to /EVENT_ID/noreply This returns a list of all users who have not replied to the event:
https://graph.facebook.com/331218348435/noreply
You can check if a specific user has not replied to an event by issuing an HTTP GET to /EVENT_ID/noreply/USER_ID. These operations require the user_events or friends_events permissions for non-public events and return an array of objects with the name, id, and rsvp_status fields. When checking a single user, an empty data will be returned if the user did reply to the event.
You can read the photos published to an event by issuing an HTTP GET request to /EVENT_ID/photos with a user access_token.
The API returns an array of photo objects.
You can post photos to an Event's Wall by issuing an HTTP POST request to EVENT_ID/photos with the publish_stream permission and the following parameters.
| Parameter | Description | Type | Required |
|---|---|---|---|
source |
Photo content | multipart/form-data |
yes |
message |
Photo description | string |
no |
If the create is successful, you get the following return.
| Name | Description | Type |
|---|---|---|
id |
The new photo ID | string |
You can read the videos published to an event by issuing an HTTP GET request to /EVENT_ID/videos with a user access_token.
The API returns an array of video objects.
You can publish a video to an event by issuing an HTTP POST request to https://graph-video.facebook.com/EVENT_ID/videos with a user access_token and the following parameters:
| Parameter | Description | Type | Required |
|---|---|---|---|
source |
Video content | multipart/form-data |
yes |
title |
Video title | string |
no |
description |
Video description | string |
no |
If the create is successful, you get the following return.
| Name | Description | Type |
|---|---|---|
id |
The new video ID | string |