Skip to main content
Before your app can be listed in the OrbitForms marketplace, it must go through our review process. This ensures all apps meet our quality and security standards.

​
Review Timeline

3-5 Business Days — Average review time for most applications.
Complex apps or those requiring additional security review may take longer. You’ll receive email updates at each stage of the process.

​
Review Stages

Prepare Submission

Complete your app profile, add screenshots, and ensure all required fields are filled.

Initial Review

Our team reviews your app configuration, permissions, and user experience.

Security Assessment

We verify OAuth implementation, data handling, and security best practices.

Feedback & Revisions

If needed, we’ll request changes. You can update and resubmit your app.

Approval & Publication

Once approved, your app will be listed in the OrbitForms marketplace.

​
Submission Checklist

Ensure your app meets these requirements before submitting:

​
Required

  • App name and description
  • Website URL
  • Privacy policy URL
  • Terms of service URL
  • Valid OAuth callback URLs

​
Optional

  • App icon (image up to 5MB)
  • Documentation link

​
Common Rejection Reasons

Avoid these common issues that can lead to rejection:
  • Missing or invalid privacy policy
  • Requesting unnecessary permissions
  • Insecure OAuth implementation
  • Poor user experience or confusing flows
  • Misleading app name or description
  • Non-functional features or broken links

​
After Approval

Marketplace Listing

Your app will appear in the OrbitForms integrations directory.

User Reviews

Users can rate and review your app publicly.

Ongoing Compliance

Maintain quality standards to keep your listing active.

Updates

Name, description, branding, URLs and your workflow actions change instantly. Additional scopes, additional redirect URIs and appearing in workflows need approval; see below.

​
Changing an approved app

An approved app never goes offline for a change. Edit it in the Developer Portal as usual; what happens next depends on the field: One change request is open at a time; saving another set of additions replaces it, and you can withdraw it from the app page. We review change requests the same way as new apps, usually within a few business days, and email you the decision. When a scope is approved, people who already authorized your app are asked for it the next time they go through the consent screen; the API tells you which scopes a token holds. Over the API, PATCH /api/developer/apps/:id answers with pending_approval (the keys that went into a change request) and change_request; GET returns pending_change_request; DELETE /api/developer/apps/:id/change-request withdraws it.

​
Need help with your submission?

Our developer relations team is here to help you through the review process. Reach out if you have questions or need guidance.

Contact Support

Get help from our developer relations team.