Please use the request channel for requests. Do not format actions as requests (e.g. "Sam "wants" you to try this "game").

Before submitting an action for approval, you must publish this action at least once through your app and verify its successful publication.

If your app publishes built-in watch actions for video, you must give users clear, ongoing, and in-context messaging (such as on the page where the user watches the video) that their watch actions will be published on Facebook.

If your app uses built-in action types such as Read, please ensure that your app adheres to the requirements for the use of each built-in action type.

If your submitted action uses specific capabilities such as user message or tagging, please ensure that your app adheres to the requirements for the use of each capability.

Please submit your action, object and usage instructions in English.

Multiple objects: Do not submit duplicate / synonymous actions (e.g. do not submit action:run and object:race, as well as action:run and object:marathon. Instead, submit one action (run) with two objects (race, marathon).

For perpetual actions (e.g. "love", "want", "need"), users don't stop loving, wanting, or needing the objects they are taking the action against so until we offer the option to make an action perpetual, please set the action end time to far in the future. E.g. Brion loves "movie title", Brion wants "world peace".

Appropriate language: No hateful, sexually explicit or misleading actions or objects. All action and objects must be comply with our terms.

Simple grammar: Wording for actions should be as simple as possible (e.g, “playing” vs. “has been playing”) and make sense; we may reject submissions if they are overly descriptive or convoluted. Keep the user experience at top of mind.

Include robust reproduction test steps when submitting actions for approval in the App Dashboard.

Ensure that the test account created during the submission process is able to reproduce and publish all submitted actions using the reproduction steps.

Ensure the icon, headline, and description are properly configured in the permissions dialog.

Sensitive actions: If you're going to be using actions related to user location or purchasing, you must disclose this in the description field of the permissions dialog or clearly within the app. Users should never be surprised by sharing these types of actions.

Any user privacy controls (e.g., private mode) must work as intended and comply with Facebook’s policies.

Custom buttons for actions should be consistent with the look and feel of your site and not reflect Facebook branding, functionality or appearance (including FB buttons).

As always, ensure integrations meet the Platform Policies.