---
title: "Grants a customer viewer or editor access to an audience by their email."
method: POST
path: "/audience/{audienceId}/shares"
tags: ["Audience"]
---

# Grants a customer viewer or editor access to an audience by their email.

`POST /audience/{audienceId}/shares`

## Request

- Base URL: `https://api.rapidata.ai`
- URL: `https://api.rapidata.ai/audience/{audienceId}/shares`
- Auth: OpenID Connect (`https://auth.rapidata.ai/.well-known/openid-configuration`, scopes: `openid`, `profile`, `email`, `offline_access`, `api`)

Granting editor access implies viewing, and lets the recipient manage the audience —
 including starting recruiting and rebuilding the distilling campaign, which spend the
 owner's budget. Re-sharing at the same level is idempotent.
 An email with no matching account is accepted and grants nothing; the response does not
 distinguish it from a successful share, so callers cannot probe which emails have accounts.
 Sharing a filtered audience records the share against its base audience, which covers the
 base and every filtered audience derived from it.

## Path parameters

- `audienceId` string, required

## Request body

- ShareAudienceWithCustomerEndpointInput
  - `email` string, required: The email of the account to share the audience with.
  - `level` 'Viewer' | 'Editor', required

## Response `204`

No Content

## Other responses

- `400`: Bad Request
- `401`: Unauthenticated
- `403`: Forbidden

## Changes

- **2026-09-04** `9da534659e5f`: 1 info
  - the security scope `api` was added to the endpoint's security scheme `OpenIdConnect`
- **2026-08-31** `f5235270ce3c`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/rapidata/apis/rapidata-api/changes/audience/:audienceId/shares/post.md)

---

[API](https://skmtc.dev/rapidata/apis/rapidata-api.md) - [All operations](https://skmtc.dev/rapidata/apis/rapidata-api/llms.txt) - [OpenAPI document](https://skmtc.dev/rapidata/apis/rapidata-api/revisions/004a977d7d9f?raw)