---
title: Invite people to share
description: POST /nd/api/share/invite_share: Invite people to participate in sharing interface description, including path, method, parameters and return information.
slug: api-post-nd-api-share-invite-share
lang: en
category: Sharing API
category_order: 8
order: 132
api_method: POST
api_path: /nd/api/share/invite_share
api_label: Invite people to share
keywords:
  - API
  - Invite people to share
  - /nd/api/share/invite_share
---

# Invite people to share

`POST /nd/api/share/invite_share`

## POST body parameters

| Parameter | Type | Description |
| --- | --- | --- |
| `file_id` | `string` | Required file/folder ID |
| `share_role` | `string` | Required role for these invitees |
| `emails` | `string[]` | Invitee email addresses |
| `phones` | `string[]` | Invitee phone numbers |

## Response

Fields listed in the source: `code`, `success`.

External recipients can be invited by email or phone and verify their identity through login or a verification code. The PDF uses emails[] and phones[] to denote arrays; confirm wire format. UI department invitations include descendants, but this API revision does not document a department parameter.

## Calling the Endpoint

Use `Authorization: Bearer <access_token>`. GET parameters belong in the URL query; normal business POST requests use JSON. Check HTTP status and then the business result. Confirm array serialization and ambiguous types with the deployment instead of inventing fields.

[Authentication](developer-api-auth.md) · [API overview](developer-api-overview.md)