> ## Documentation Index
> Fetch the complete documentation index at: https://developers.jup.ag/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhook Integration (V1)

> Provide RFQ liquidity to JupiterZ by hosting a quote-and-swap webhook.

This guide covers how to provide liquidity to JupiterZ, Jupiter's RFQ (Request For Quote) system, using the V1 webhook model. You host a webhook implementing the RFQ API schema, Jupiter sends it quote requests and taker-signed transactions, and your system co-signs and lands the fills.

> [!NOTE]
>
> V1 (webhook) and [V2 (gRPC streaming)](https://developers.jup.ag/docs/swap/routing/rfq/v2/streaming.md) run concurrently. V2 does not replace V1: you can integrate with either or both. They sit in different parts of Jupiter's stack: V1 works directly in the JupiterZ program and APIs (your quotes are served on the JupiterZ paths and fills settle through the [Order Engine program](https://developers.jup.ag/docs/swap/routing/rfq/v1/settlement.md#order-engine)), while V2 streams orderbooks that Metis consumes, with fills executing through the Jupiter v6 swap aggregator program.

![RFQ Flow](https://mintcdn.com/jupiter/mrenEfoqnubhOTHf/static/images/rfq-flow.png?fit=max\&auto=format\&n=mrenEfoqnubhOTHf\&q=85\&s=56ff3c769b07c067dbfcb9c49c5f157d)

## Integration process

1. Host a service that implements the RFQ webhook API schema, see [Webhook API](https://developers.jup.ag/docs/swap/routing/rfq/v1/webhook-api.md).
2. Complete the acceptance and integration tests from the [rfq-webhook-toolkit](https://github.com/jup-ag/rfq-webhook-toolkit).
3. Register your webhook with Jupiter. You will be onboarded to Edge (pre-production) before going live.

The [rfq-webhook-toolkit](https://github.com/jup-ag/rfq-webhook-toolkit) repository owns the code-level mechanics:

* [Sample server](https://github.com/jup-ag/rfq-webhook-toolkit/tree/main/server-example): a Rust implementation of the webhook API.
* [OpenAPI schema](https://github.com/jup-ag/rfq-webhook-toolkit/tree/main/openapi): the exact request and response shapes for every endpoint.
* [Integration tests](https://github.com/jup-ag/rfq-webhook-toolkit/tree/main/tests): acceptance tests (offline, against your webhook) and integration tests (against Edge, real mainnet swaps).
* [Troubleshooting](https://github.com/jup-ag/rfq-webhook-toolkit/blob/main/tests/README.md#troubleshooting): common issues during integration.

> [!NOTE]
>
> To register your webhook and begin onboarding, submit a request through the [support form](https://support.jup.ag/requests/new). For pre-integration questions, ask in the [developer support channel](https://discord.com/channels/897540204506775583/910250162402779146) on Discord.

## Continue

> [card] [Webhook API](https://developers.jup.ag/docs/swap/routing/rfq/v1/webhook-api.md)
>
> The endpoints your service implements, response codes, timeouts, token advertising, and IDs.

> [card] [Quoting and fills](https://developers.jup.ag/docs/swap/routing/rfq/v1/quoting.md)
>
> Fulfillment requirements, quote expiry, and how fees are applied.

> [card] [Settlement and special cases](https://developers.jup.ag/docs/swap/routing/rfq/v1/settlement.md)
>
> The Order Engine program, Squads multisig takers, the circuit breaker, and testing.

> [card] [Streaming Integration (V2)](https://developers.jup.ag/docs/swap/routing/rfq/v2/streaming.md)
>
> The gRPC streaming model, an alternative that runs concurrently with V1.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.