GET /api/v1/sales-closers/{closerId}/meeting-link
Reads or replaces an eligible closer’s default meeting URL. Defaults are copied into new bookings; existing calls keep their own link.
| Role in the organization | This endpoint |
|---|---|
OWNER | Allowed with current organization permissions |
ADMIN | Allowed with current organization permissions |
MEMBER | Conditional on the business role and scope below |
| Requirement | Rule for this endpoint |
|---|---|
| Business role | Closer for their own default; no setter access |
| Resource scope | Organization bound to the API key |
| Participation | Target must be an eligible closer in this organization |
| Resource state | No additional state restriction |
| Parameter | Type | Required | Description |
|---|---|---|---|
closerId | UUID | yes | Closer user identifier |
| Header | Required | Description |
|---|---|---|
x-api-key | yes | Organization API key |
X-Correlation-Id | no | Correlation UUID for support |
curl -X GET "$COHORTE_API_BASE_URL/api/v1/sales-closers/11111111-1111-4111-8111-111111111111/meeting-link" \
-H "x-api-key: $COHORTE_API_KEY"200: successful read, save or replay.400: invalid identifier, payload or missing idempotency key.401: invalid key or membership.403: insufficient permissions.429: rate limit reached.500: unexpected failure.| Field | Type | Nullable | Description |
|---|---|---|---|
success | boolean | no | Successful request |
data.closerId | UUID | no | Closer user identifier |
data.meetingUrl | string | yes | Default link, or null when unset |
{
"success": true,
"data": {
"closerId": "11111111-1111-4111-8111-111111111111",
"meetingUrl": null
}
}This read changes nothing.
Changing or clearing the default affects future reservations only. No email is sent. When a call is reassigned, its saved link is replaced by the new closer’s default at that moment, or cleared if they have none.
The response also includes nullable contactEmail and effectiveEmail. The professional address takes priority; when empty the closer’s account email is used for booking Reply-To and closer communications. Login identity is unchanged. These fields have the same organization and closer scope as the meeting default.