如何通过Facebook API设置「不参加」「不感兴趣」活动状态及移除已有状态？

Nice question! Let’s walk through exactly how to handle these event status actions via the Facebook Graph API, mirroring the exact button clicks you’d do on the Facebook website.

Prerequisites First #

Before diving into the actions, make sure you’ve got these covered:

• You need the rsvp_event permission granted by the user (this is mandatory for all RSVP-related API calls)
• Use a valid user access token (not an app token—only user tokens have the context to modify a specific user’s event status)

Setting "Not Going" or "Not Interested" Statuses #

For both of these statuses, you’ll send a POST request to the event’s RSVPs endpoint, specifying the corresponding status parameter. Here’s how each works:

Set "Not Going" #

This matches clicking the "Not Going" button on the Facebook event page:

POST /{event-id}/rsvps
Parameters:
  status: declined
  access_token: {user-access-token}

Set "Not Interested" #

This is equivalent to selecting the "Not Interested" option on the event:

POST /{event-id}/rsvps
Parameters:
  status: not_interested
  access_token: {user-access-token}

Removing Existing "Going" or "Interested" Statuses #

To undo a "Going" or "Interested" RSVP (i.e., revert back to having no stated status, just like clicking the "Undo" button on Facebook), you have two reliable options:

Option 1: Delete the RSVP Record #

The cleanest way is to delete the existing RSVP entry for the user. This directly removes their status entirely:

DELETE /{event-id}/rsvps/{user-id}
Parameters:
  access_token: {user-access-token}

Option 2: Update to "Unsure" (Alternative) #

If you prefer a POST-based approach (some systems handle POST more easily than DELETE), you can set the status to unsure. Note that this sets the status to "Maybe" instead of fully removing it, so only use this if that’s acceptable for your use case:

POST /{event-id}/rsvps
Parameters:
  status: unsure
  access_token: {user-access-token}

Key Things to Keep in Mind #

• Always check that your access token has the rsvp_event permission before making calls—you’ll get a permission error if it’s missing.
• Some events (like private ones where the host restricted RSVP changes) might block these actions, so make sure to handle error responses gracefully.
• Double-check that the event ID is valid and the user has access to the event (e.g., they weren’t removed from a private event’s guest list).

内容的提问来源于stack exchange，提问作者Alex Kumundzhiev