---
title: "Create Event"
method: POST
path: "/v1/installations/{integrationConfigurationId}/events"
tags: ["marketplace"]
---

# Create Event

`POST /v1/installations/{integrationConfigurationId}/events`

Partner notifies Vercel of any changes made to an Installation or a Resource. Vercel is expected to use `list-resources` and other read APIs to get the new state.<br/> <br/> `resource.updated` event should be dispatched when any state of a resource linked to Vercel is modified by the partner.<br/> `installation.updated` event should be dispatched when an installation's billing plan is changed via the provider instead of Vercel.<br/> <br/> Resource update use cases: <br/> <br/> - The user renames a database in the partner’s application. The partner should dispatch a `resource.updated` event to notify Vercel to update the resource in Vercel’s datastores.<br/> - A resource has been suspended due to a lack of use. The partner should dispatch a `resource.updated` event to notify Vercel to update the resource's status in Vercel's datastores.<br/>

## Path parameters

- `integrationConfigurationId` string, required

## Request body

- object
  - `event` union, required
    - object
      - `type` 'installation.updated', required
      - `billingPlanId` string — The installation-level billing plan ID
    - object
      - `type` 'resource.updated', required
      - `productId` string — Partner-provided product slug or id
      - `resourceId` string, required — Partner provided resource ID

## Response `201`

## Other responses

- `400` — One of the provided values in the request body is invalid. One of the provided values in the request query is invalid.
- `401` — The request is not authorized.
- `403` — You do not have permission to access this resource.
- `404`
- `410`

---

[API](https://skmtc.net/vercel/apis/api.md) · [All operations](https://skmtc.net/vercel/apis/api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/vercel/api/versions/61d1ba3f6dac/schema)