---
title: "/signups/{eventSignupId}"
method: PUT
path: "/signups/{eventSignupId}"
---

# /signups/{eventSignupId}

`PUT /signups/{eventSignupId}`

## Request

- Base URL: `https://api.securevan.com/v4`
- URL: `https://api.securevan.com/v4/signups/{eventSignupId}`
- Auth: HTTP basic

Use this endpoint to update a specific existing Signup. A record of this change is displayed in the VAN UI.

A Signup’s Event and Person properties are immutable after creation. If you want to sign up a Person for a different Event, first [delete](ref:signups#signupeventsignupid-2) the existing Signup and [create](ref:signups#signups-2) a new one.

If you do not know the `eventSignupId`, consider using the [create or modify](ref:signups#signups-2) endpoint.

When a Signup is updated, a [canvass response](ref:people#peoplevanidcanvassresponses) is generated to represent the signup interaction. The *Input Type* is API, the *Date Canvassed* is the current date, the *Canvasser* is the API user associated with the current context, and the *Result Code* corresponds to a result most appropriate for the given Status (e.g., *Scheduled* → *Canvassed*). Consult the VAN UI for a detailed mapping.

## Path parameters

- `eventSignupId` integer, required

## Request body

- object
  - `eventSignupId` integer
  - `person` object
    - `vanId` string
  - `event` object
    - `eventId` integer
  - `shift` object
    - `eventShiftId` integer
  - `role` object
    - `roleId` integer
  - `status` object
    - `statusId` integer
  - `location` object
    - `locationId` integer

## Response `204`

204

## Other responses

- `400`: 400
- `404`: 404

## Changes

- **2026-11-03** `4f2049fba5af`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/ngpvan/apis/van-crm/changes/signups/:eventSignupId/put.md)

---

[API](https://skmtc.dev/ngpvan/apis/van-crm.md) - [All operations](https://skmtc.dev/ngpvan/apis/van-crm/llms.txt) - [OpenAPI document](https://skmtc.dev/ngpvan/apis/van-crm/revisions/4f2049fba5af?raw)