Skip to main content
PUT
/
meetings
/
{meeting_sid}
/
spots
/
{id}
Update a spot
curl --request PUT \
  --url https://{your-workspace}.neetocal.com/api/external/v1/meetings/{meeting_sid}/spots/{id} \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: <x-api-key>' \
  --data '{
  "spot": "custom",
  "spot_phone_call_number": null,
  "spot_custom_text": "Custom meeting instructions",
  "spot_in_person_location": null,
  "is_default": true
}'
{
  "message": "Spot updated successfully",
  "spot": {
    "id": "1d35e633-71b9-4ad9-b659-b034f361539b",
    "spot": "in_person",
    "spot_phone_call_number": null,
    "spot_custom_text": null,
    "spot_in_person_location": "123 Main St, Suite 100, City, State 12345",
    "is_default": true,
    "created_at": "2025-01-15T10:30:00Z",
    "updated_at": "2025-01-15T10:30:00Z"
  }
}
Replace {your-workspace} with your workspace’s subdomain.
Learn how to find your subdomain in Identifying your subdomain.

Headers

​
X-Api-Key
string
required

X-Api-Key is used to authenticate requests using an API key. Provide your API key in this header to access protected endpoints. Refer to Authentication for more information.

Path Parameters

​
meeting_sid
string
required

The unique identifier (SID) of the scheduling link you want to use. You can get sid in different ways. Visit the scheduling link page and then click on "Settings" > "Show SID". That will give you sid. You can also get this from the response of the List all scheduling links endpoint, where it appears as the sid property for each scheduling link in the response.

Example:

"vj5pgkh"

​
id
string
required

The unique identifier of the spot. You can get this id from the response of the List spots for a meeting endpoint, where it appears as the id property for each spot in the response.

Example:

"1d35e633-71b9-4ad9-b659-b034f361539b"

Body

application/json
​
spot
enum<string>

The new spot type (must be one of the predefined values).

Available options:
daily,
zoom,
jitsi,
google_meet,
teams,
whereby,
in_person,
custom,
phone_call
Example:

"custom"

​
spot_phone_call_number
string | null

Phone number for phone call spots. Only required when spot type is "phone_call".

Example:

null

​
spot_custom_text
string | null

Custom text for custom spots. Only required when spot type is "custom".

Example:

"Custom meeting instructions"

​
spot_in_person_location
string | null

Location details for in-person meetings. Only required when spot type is "in_person".

Example:

null

​
is_default
boolean

Whether this spot should be the default option.

Example:

true

Response

200 - application/json

OK - Request succeeded

​
message
string
Example:

"Spot updated successfully"

​
spot
object