> For the complete documentation index, see [llms.txt](https://api-docs.visadoc.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-docs.visadoc.co/trip-changes-and-erasure.md).

# Trip changes and erasure

What to do when a trip changes, at each stage of a case, and what erasing a traveller removes.

Travel plans change. What you can do about it depends on the stage the case has reached.

v3 has **no endpoint to edit** an assessment or an application. Changes happen either through a new assessment or inside VisaDoc, on the case itself.

## Minor vs material changes

* **Minor changes** (travel dates that don't affect eligibility, hotel, itinerary, contact details): the case is updated in VisaDoc and the process continues.
* **Material changes** (purpose / activity, destination, nationality or residency, visa route, or date changes that affect eligibility): run a new `POST /assessments/new` to revalidate the visa requirements, and start a new application if the result calls for it.

## By stage

| Stage              | Statuses                                   | Trip changes                                                                                                                                |
| ------------------ | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Not started        | `created`, `draft`                         | Run a new assessment                                                                                                                        |
| Opened             | `New Application`                          | Run a new assessment and create a new application                                                                                           |
| In preparation     | `Documents`, `Profile`, `Application Form` | The traveller works through the changes with their assigned VisaDoc case manager. A person decides which changes the application can absorb |
| With the authority | `Submission to Embassy`, `In Embassy`      | No changes, except additional documents the embassy asks for                                                                                |
| Completed          | `Decision Made`                            | No changes. For a new trip, run a new assessment                                                                                            |

Once a case is with the authority, it can't be changed. Plan your own amend flows around that point: check the case's `status` with `GET /applications/{application_id}` before you offer a change to the traveller.

## Erasing a traveller (GDPR)

`DELETE /applicants/{applicant_id}` erases a traveller's personal data and keeps anonymised records:

| Erased                                                      | Kept                                                                                 |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| The traveller's name, email, company and other profile data | The traveller's system ID                                                            |
| Application form answers                                    | Each application's visa type, nationality, destination, activity category and status |
| Uploaded documents and the data extracted from them         |                                                                                      |

The kept records carry no personal data, so you and VisaDoc keep the billing and compliance history (for example, "an anonymous traveller obtained a business visa for Germany") without being able to identify the person.

Things to know before you call it:

* **Erasure is permanent.** There's no undo.
* **Erase after the case is complete.** Erasure removes the documents and form answers an in-progress case depends on.
* The response is an empty object on success.