For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HomepageProduct HelpLog inTry for Free
Developers HomeAPI ReferenceMCP
Developers HomeAPI ReferenceMCP
    • Developers Home
  • Build an Integration
    • Overview
    • Create an OAuth App
    • Publish
  • External Links
    • Integrations Directory
    • Product Help
    • Product Updates
    • Making of Close Blog
    • Open Source (GitHub)
Close

Product

OverviewCommunicationAutomationIntegrationsReportingSMSCallingSecurityForms

Pricing & Use Cases

PricingClose vs Other CRMsCustomer Stories

Resources

Sales BlogSales ResourcesSales GuidesWebinarsOn-Demand DemoSales Tools

Company

AboutCareersPartner with CloseBrand GuidelinesTermsPrivacyGDPRCCPA

Get Help

+1-833-GO-CLOSEHelp CenterDownload the Close AppProduct UpdatesSystem Status
LogoLogo
HomepageProduct HelpLog inTry for Free
On this page
  • Private vs. public apps
  • Making your app public
  • Getting listed in the Integrations Directory
  • Requirements
  • How to apply
Build an Integration

Publish

Make your OAuth app public and get listed in the Close Integrations Directory.
||View as Markdown|
Was this page helpful?
Edit this page
Previous

Creating an OAuth App

Built with

Private vs. public apps

OAuth apps are Private by default, meaning only members of your own Close organization can authorize them. This is fine if you and your teammates are the only users.

If you want any Close user to be able to authorize your app, you need to make it Public.

Making your app public

  1. Go to Settings → Developer → OAuth Apps and select your app.
  2. Click Make Public and submit for review.
  3. We’ll review your app and reply by email.

Once approved, your app will be marked as Public and any Close user will be able to authorize it.

Getting listed in the Integrations Directory

After your app is public, you can apply to have it listed in the Close Integrations Directory — making it discoverable by thousands of Close customers and linking directly to your product.

Requirements

  • Your integration must be publicly available (not internal-only).
  • It must use OAuth 2.0 for authentication (not API keys).
  • It should provide clear value to Close users.

How to apply

Email support@close.com with:

  • Your integration name and description
  • A link to your product
  • A brief explanation of what it does with Close
  • Your OAuth App’s Client ID