The Marketplace API consists of two sets of endpoints: the Partner API (called by Vercel) and the Vercel API (called by your integration). Together, they enable your integration to manage installations, provision resources, and handle billing.
When a customer uses your integration, these two APIs communicate to handle the integration lifecycle:
- Vercel calls Partner API — When users install, configure, or interact with your integration, Vercel sends requests to your integration server
- Integration calls Vercel API — Your server makes requests to Vercel to get account info, manage resources, submit billing data, and more
See Native Integration Flows to understand how these APIs work together throughout the installation and usage lifecycle.
Vercel calls these endpoints on your integration server. Implement them to handle installation lifecycle, resource provisioning, and billing operations.
- GETGet InstallationOptional
- PUTUpsert InstallationRequired
- PATCHUpdate InstallationOptional
- DELETEDelete InstallationRequired
- GETList Resources (Deprecated)Deprecated
- POSTProvision ResourceRequired
- GETGet ResourceRequired
- PATCHUpdate ResourceOptional
- DELETEDelete ResourceRequired
- POSTRequest Secrets RotationOptional
- POSTResource REPLOptional
- GETList Billing Plans For ProductRequired
- GETList Billing Plans For ResourceOptional
- GETList Billing Plans For InstallationOptional
- POSTProvision PurchaseOptional
Your integration calls these endpoints on Vercel servers to interact with resources like projects, deployments, billing, and configuration.
- Marketplace API Overview — Learn about authentication and common patterns
- Native Integration Concepts — Understand installations, resources, and configurations
- Webhooks Documentation — Handle real-time events from Vercel