What we look for
- It works today with a public PostNimbo surface: the REST API, an OAuth app, webhooks or the MCP connector.
- Users connect it with OAuth and PKCE, and it asks for the fewest scopes it needs. Never ask users for their password or for an API key when OAuth works.
- It respects rate limits and Retry-After, and keeps working when a member revokes it or loses access to a brand.
- It says what it reads and stores, deletes that data when it is disconnected, and never sells it or uses it for advertising.
- Its name does not suggest it is made by PostNimbo: “for PostNimbo” is fine, “PostNimbo Pro” is not.
What to send
- The app name, a 512 px square icon, a one-line summary (up to 120 characters) and a longer description.
- The category: Social channels, AI assistants, Create & find content, Automation & workflows, Browser & calendar or Developer tools.
- What it can see and do in PostNimbo, in plain words, and the scopes it asks for.
- How to connect it, step by step, and a support email.
- Links to your privacy policy and terms, and a test account or a short video for the review.
Review
- 1Email the details above to support@postnimbo.com.
- 2We connect it to a test workspace and check the points above.
- 3Once it passes, it appears in the App directory with its status for each workspace. We may remove a listing that stops working or breaks these rules.