Workplace from Meta is going away. You will be able to continue using Workplace until 31 August 2025. Visit our Help Center to find out more.
/{group-id}
Represents a Workplace group. The /{group-id}
node returns a single group.
There are specific considerations which should be taken into account when accessing multi-company groups:
WORK_MULTI_COMPANY
id
, name
and picture
will be visible if an app is from a different company to the userYou can read information about a group by making a Graph API GET
request to /{group-id}
.
Reading Group node requires the Read group content permission.
Field Name | Description | Data Type |
---|---|---|
| The group ID. |
|
| Information about the Group's cover photo. | |
| A URL containing an image for the group cover photo. |
|
| A brief description of the group. |
|
| The URL for the group's icon. |
|
| Indicates whether the group is a default Workplace group (read only). |
|
| Indicates whether the group is also a community and can contain other groups (read only). |
|
| The name of the group. |
|
| The member that created this group. | |
| The privacy setting of the group. Possible values:
|
|
| The last time the group was updated. This includes any changes in the group's properties and changes in posts and comments. |
|
| Indicates whether the group was archived. |
|
| Indicates whether posts to the group will require admin approval. |
|
| Indicates the purpose of the group |
Deprecated: |
| Indicates if a post requires admin approval. |
|
| Indicates how new members can join the group. |
|
| Indicates the order of posts returned for |
|
| Indicates whether the group is an Official Workplace Group. An official-group icon will appear alongside the official group’s name in product. |
|
You can't publish using this edge. In order to create a group, publish to the /community/groups
edge.
You can't delete a group using this node. Removing the last member of a group will delete that group automatically.
You can update a group by making a Graph API POST
request to /{group-id}
and passing values for the fields to be updated in the request body.
Making updates to a group node requires the Manage groups permission.
Edge Name | Description |
---|---|
The admins of a Workplace group. Addition and Deletion of admins supported on Workplace. Refer examples given below. | |
The photo albums in a Workplace group. | |
The rules for adding members automatically to a group. | |
The docs in a Workplace group. | |
The events in a Workplace group. | |
The posts in a Workplace group, arranged into a feed. | |
The files shared into a Workplace group. | |
| The pending membership requests for groups that have membership approvals enabled. |
The members of a Workplace group. This edge exposes:
| |
| The moderators of a Workplace group. |
| The post pinned to the group. |
| List any child groups (only applicable to groups which are also communities) |
GET graph.facebook.com
/{group-id}?fields=id,name,archived,privacy
POST graph.facebook.com
/{group-id}?archive=true
GET graph.facebook.com
/{group-id}/members?fields=name,id,joined
GET graph.facebook.com
/{group-id}?fields=admins,moderators
GET graph.facebook.com
/{group-id}/docs
GET graph.facebook.com
/{group-id}/feed
GET graph.facebook.com
/{group-id}/feed?sorting_setting=RECENT_ACTIVITY
Parameters
sorting_setting
Allows ordering of posts by the time they were last updated instead of created when set to RECENT_ACTIVITY
. The default behaviour can be set explicitly by using CHRONOLOGICAL
as value. Updates may include edits to the post as well as a comment or reaction having been added.
GET graph.facebook.com
/{group-id}/feed?fields=attachments
Poll options are listed in descending order according to vote count for each option.
GET graph.facebook.com
/{group-id}/members?fields=name,joined
POST graph.facebook.com
/{group-id}/members/{member-id}
POST graph.facebook.com
/{group-id}/members?email=michael%40example.com
When including email addresses in the URL for a request, ensure that the email addresses is URL encoded. Example: michael@example.com
becomes michael%40example.com
.
Removing the last member from a group will schedule that group for deletion.
DELETE graph.facebook.com
/{group-id}/members/{member-id}
DELETE graph.facebook.com
/{group-id}/members?email=michael%40example.com
When including email addresses in the URL for a request, ensure that the email addresses is URL encoded. Example: michael@example.com
becomes michael%40example.com
.
POST graph.facebook.com
/{group-id}/admins/{user-id}
DELETE graph.facebook.com
/{group-id}/admins/{user-id}
POST graph.facebook.com
/{group-id}/events
?name=New+Event
&start_time=2017-03-02T14:00:04+00:00
&end_time=2017-03-02T15:00:04+00:00
&description=Test+Description
&location=Boardroom
POST graph.facebook.com
/{group-id}/photos?source={image-data}
POST graph.facebook.com
/{group-id}/photos?url={image-data}
POST graph.facebook.com
/{group-id}/feed?attached_media=[{"media_fbid":"{photo-id}"},{"media_fbid":"{photo-id}"}]
Parameters
attached_media
Used for photos & videos, an array of media_fbids
wrapped in braces. Supports the following image formats: .jpeg, .bmp, .png, .gif, .tiff. More information about image formats can be found here. Supported video files can be found here. To obtain media_fbids
for images, please publish unpublished photos to https://graph.facebook.com/me/photos
first, as described in the documentation here. To obtain media_fbids
for videos (including animated GIFs), please publish videos first to https://graph.facebook.com/me/videos?no_story=true
.
Setting the paramater no_story
to true suppresses the feed story that is automatically generated on a person’s profile when they upload a video using your app.
POST graph.facebook.com
/{group-id}/feed?files=[{file-id},{file-id}]
Parameters
files
Used for files, an array of file_ids
(note they are not wrapped in braces). File versioning is not currently supported. To update files, please remove the original file from the post attachments and re-upload a new file attachment. Supports the following file formats:
To obtain file_ids
, please publish files to https://graph.facebook.com/group_file_revisions
first. You may publish source files locally from your computer.
You cannot combine the attached_media
and files
parameters in one API call. This mimics behavior in the group composer, which has separate options for uploading a 'Photo/Video' and 'File'.
POST graph.facebook.com
/{group-id}/?post_permissions=NONE&join_setting=ADMIN_ONLY&purpose=WORK_SOCIAL&post_requires_admin_approval=false
GET graph.facebook.com
/{group-id}/pinned_posts?fields=reactions,comments
GET graph.facebook.com
/{group-id}?fields=is_community
GET graph.facebook.com
/{group-id}/auto_membership_rules
Example Response (JSON):
{ "data": [ { "conditions": [ { "field": "TITLE", "operator": "CONTAINS", "values": [ "sales" ] } ], "id": RULE_ID } ], ... }
DELETE graph.facebook.com
/RULE_ID
POST graph.facebook.com
/{group-id}/auto_membership_rules
Example Payload:
{ "conditions": [ { "field": "LOCATION", "operator": "CONTAINS", "values": ["London", "San Francisco"] } ] }
This API has the potential of adding thousands of users to a group if a mistake is made, so it’s extremely important to use this carefully and double-check before executing the API call.
GET graph.facebook.com
/{group-id}?fields=id,is_official_group
POST graph.facebook.com
/{group-id?is_official_group={FALSE | TRUE}