6 min read

Overview

The QuickNode Marketplace enables direct distribution of your services to hundreds of thousands of existing and future QuickNode developers. It is an effective way to integrate your product into the web3 development stack.

This guide provides a step-by-step path to take your idea from concept to a published add-on.

Why Build on the QuickNode Marketplace?

Building on the QuickNode Marketplace provides a powerful platform to launch, distribute, and monetize your services. Here are the key benefits for our partners:

• Massive Distribution: Gain immediate access to QuickNode's large and growing user base of developers and enterprises. Increase the visibility and adoption of your product by placing it directly in their workflow.
• Effortless Monetization & Operations: We handle the complexities of user management, billing, and rate limiting, allowing you to focus on your core product. You can easily monetize your add-on and choose to receive payments in fiat or cryptocurrency.
• Purpose-Built Developer Tools: Accelerate your workflow with tools built for you. We provide a testing CLI to speed up validation and offer starter code templates in multiple languages (Python, Go, JavaScript, and more) to get you building in minutes.
• Proven Reliability & Performance: Your add-on can be integrated with QuickNode's high-performance, battle-tested infrastructure, ensuring it performs optimally and reliably for users worldwide.
• Dedicated Partnership & Support: Our Marketplace team collaborates with you throughout the development and post-launch stages. From technical assistance to co-marketing, we are invested in your success.

How to Launch Your Add-on

The process of launching your add-on involves four main steps. Each step involves development on your side and a review by the QuickNode team to ensure quality and security for our users.

1. Become a Marketplace Partner: Get your official developer account.

2. Design & Build Your Add-on: Choose your add-on type and build it.

3. Submit for Internal Review: Get your add-on technically validated by the QuickNode team.

4. Launch in Beta & Gather Feedback: Release your add-on to the public for early testing.

5. Go Live for General Availability: Move from beta to a full public launch.

Now, let's dive into each step in detail.

Step 1: Become a Marketplace Partner

Before you can build, you need a partner account. This gives you access to the Marketplace dashboard where you'll create and manage your add-ons.

To get started, you’ll need to register for a developer account in order to publish add-ons on the QuickNode Marketplace. From your QuickNode dashboard, select the Switch to Partners option in the left-hand navigation menu, then complete the Marketplace account application. Here’s a preview of the form:

The approval process typically takes 1-2 business days. You'll be notified via email once your partner account is approved.

Step 2: Design & Build Your Add-on

This is the core development phase where you integrate your service with the Marketplace.

Step 2.1: Choose Your Add-on Type

When creating an add-on for the QuickNode Marketplace, you can choose from three main types depending on what you want to provide:

• JSON-RPC Add-Ons: Extend QuickNode’s core RPC with custom methods that go beyond the standard JSON-RPC methods.

  Example: BTC Blockbook JSON-RPC adds a bb_getBalanceHistory method to fetch historical balance data for Bitcoin addresses.

• REST Add-Ons: Provide RESTful APIs to expose new data or functionality. These are ideal for interacting with blockchain data or external services using standard HTTP operations (GET, POST, PUT, DELETE).

  Example: Aerodrome Swap API offers endpoints like GET v1/pools and POST v1/swap/build to deliver swap quotes and build transactions across multiple blockchains.

• External Add-Ons: These add-ons can be APIs hosted outside QuickNode or web apps accessible via Single Sign-On (SSO).

  Example: Covalent’s GoldRush Wallet API lets developers obtain an API key and access wallet data directly through their own service.

Step 2.2: Choose an Authentication Method

QuickNode supports several authentication options to help you control access to your add-on. Pick the one that matches how your service is designed:

• Header-Based Authentication: Use a custom HTTP header (like x-api-key) to authenticate requests. This is the easiest choice if your API already supports header-based auth, since it requires no changes.

• HTTP Basic Auth: Protects your endpoints with a single username and password used for all Marketplace traffic. This option is simple to set up and only requires minor code updates.

• Provisioning APIs: Gives you full control of customer accounts by implementing endpoints to create, update, and remove users. Best for add-ons that manage user-specific data or services, since you can handle the lifecycle directly.

Note: Add-ons that include a dashboard or support SSO login are required to use Provisioning APIs.

• No Authentication: For fully public services that don’t need access control. Requests from QuickNode users are passed directly to your API with no auth headers.

Authentication Methods

For more details on each method, see our Authentication Methods Guide.

Step 2.3: Develop Your Add-on

With your add-on type and authentication method decided, it’s time to start building. We provide several resources to make development straightforward and efficient.

Follow our comprehensive How to Build a Marketplace Add-On guide for step-by-step instructions. This guide covers:

• Detailed instructions for each add-on type
• Code samples in multiple programming languages (Python, Go, JavaScript, etc.)
• Best practices for testing

Add-On Development Course

For a hands-on learning experience, check out the Marketplace Add-On Development Course. In this course, we build a fully functional RPC add-on (Block Timestamp Lookup) from scratch, covering every step of the process.

Step 3: Configure & Submit for Internal Review

Once your add-on is developed, you need to configure it in the partner dashboard and submit it for a technical review. This step ensures your service is stable, secure, and correctly integrated before it becomes publicly accessible.

Step 3.1: Prepare Your Add-on Details

The submission form in the partner dashboard is where you define every aspect of your add-on. To complete it, you will need to provide three main categories of information:

• Listing & Marketing Details: This includes your add-on's name, description, icon, and screenshots that will be displayed in the Marketplace.

• Technical Configuration: You will specify your add-on type, provide service URLs, define RPC methods or REST endpoints (if applicable), and list supported chains.

• Business Model: Here you will outline the features of your add-on and structure your pricing plans (e.g., Free, Pro, Enterprise).

Preparing Your Listing

For best practices on creating your listing details, icons, screenshots, and pricing plans, see our Marketing & Business Details guide.

Step 3.2: Fill Out the Submission Form

Once you have entered all the required details in the submission form, you are ready to send it to our team.

Before hitting the submit button, perform a final check to ensure that all your service URLs (including your API endpoint and health check) are functional and publicly accessible. Verifying this beforehand helps prevent common delays in the review process.

Publishing Your Add-on

For a detailed guide on how to publish your add-on, from filling out the submission form to the general availability launch, see our How to Publish Your Add-on guide.

Step 4: Launch in Beta & Gather Feedback

After your add-on successfully passes the internal review, it will be published on the Marketplace with a Beta tag. This makes your service publicly accessible to all QuickNode users, allowing you to gather real-world feedback from early adopters before a full launch.

This is the time to execute your beta testing strategy. Announce the release to your community and engage with users to collect valuable feedback on functionality, user experience, and documentation. This feedback will help you refine your add-on and make it more user-friendly.

Step 5: Go Live for General Availability

The final step is to move from beta to a full public launch. This transition to General Availability (GA) removes the Beta tag and presents your add-on as a fully supported solution in the Marketplace.

Once you have gathered sufficient feedback and resolved any critical issues discovered during the beta period, you can apply for General Availability from your partner dashboard.

Next Steps

You now have a clear, end-to-end understanding of what it takes to launch on the QuickNode Marketplace. The next step is to start building your add-on.

If you haven’t yet decided which authentication method to use, review the Authentication Methods for Marketplace Add-Ons guide to choose the option that best fits your service.

Once ready, follow the How to Build a Marketplace Add-On guide for detailed, step-by-step development instructions, code samples, and best practices to help you create your first add-on.

We ❤️ Feedback!

Let us know if you have any feedback or requests for new topics. We'd love to hear from you.