Will the application that pulls data from Webflow CMS and is used in a React application be publicly listed by Webflow if we have to register it?
TL;DR
- Register your app with Webflow to generate an API key and use OAuth if accessing multiple accounts.
- Public listing depends on usage; private apps aren't listed, but integrations can be listed if compliant.
- Ensure compliance with Webflow's policies and provide documentation if pursuing a public listing.
If you are developing an application that interacts with Webflow CMS and is used within a React application, here’s what you need to know about registration and public listing with Webflow:
1. Application Registration
- Webflow API Key: To interact with Webflow CMS, you'll need to register your application and generate an API key from your Webflow project settings.
- OAuth: If your application requires access to user data across multiple Webflow accounts, consider implementing OAuth for authorization.
2. Public Listing
- Public vs. Private Use: Typically, whether your application gets publicly listed by Webflow depends on how you intend to use it. Private applications for internal use do not require public listing.
- Webflow Integrations: If your application offers integration features that others can use, you may choose to pursue a listing in Webflow’s Integrations directory once your application complies with their requirements.
3. Webflow’s Requirements
- Compliance: Ensure your application complies with Webflow’s API usage policies, terms of service, and any other technical requirements they may specify.
- Documentation and Support: You may need to provide sufficient documentation and support if you aim for a public listing.
Summary
To determine whether your application will be publicly listed by Webflow, consider your usage purpose, comply with Webflow’s API policies, and decide if listing in their Integrations directory is beneficial. Private use applications typically do not get publicly listed.
