---
title: "Sync a Drip customer to Stripe (create cus_xxx and link)"
method: POST
path: "/v1/customers/{id}/sync-stripe-customer"
tags: ["Customers"]
---

# Sync a Drip customer to Stripe (create cus_xxx and link)

`POST /v1/customers/{id}/sync-stripe-customer`

Create a Stripe Customer on the merchant's connected Stripe account for the given Drip customer and persist the resulting `cus_xxx` on the Drip customer row. Idempotent: if the Drip customer already has a `stripeCustomerId`, returns it unchanged. Works with API-key or OAuth-connected Stripe integrations. Email/name are pulled from the Drip customer's `metadata.email` / `metadata.name`, falling back to `externalCustomerId` when it looks like an email, then to `emailOverride` from the request body.

> **Requires a secret key (`sk_*`) with at least the `OPERATOR` role.**

## Path parameters

- `id` string, required

## Request body

- object
  - `integrationId` string — Specific Stripe integration to use. Omit to auto-select the workspace's active Stripe integration.
  - `emailOverride` string — Email to send to Stripe when the Drip customer has none in metadata or externalCustomerId.

## Response `200`

Default Response

---

[API](https://skmtc.net/usedrip/apis/drip-api.md) · [All operations](https://skmtc.net/usedrip/apis/drip-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/usedrip/drip-api/revisions/2cb1567969ca/schema)