> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stardrift.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Remove Entry

> Remove one entry from a day — the inverse of add_place / add_day_note.

The removal is `apply_plan_actions` + `RemoveEntryAction` — the same pair
the LLM edit path uses (`plan/edit_subagent.py`, `stream_processing.py`),
rather than a second implementation of "filter the day's entries". Note the
web does NOT go through this: it removes client-side in
`lib/plan-mutations.ts` and PUTs the whole plan. What the two share is
`EditablePlan.save`, which mirrors that PUT's validate-then-save.

Nothing else is needed here: `item_refs` is a read-time derived index that
`PlanRepository.assemble_content` reconstitutes as `[]` on every load.

RemoveEntryAction filters, so removing an entry that isn't there succeeds
silently — that would report a deletion which never happened, so a missing
entry_id 404s instead.

The itinerary activity is deliberately left in place: another day may
reference it, and an orphaned activity is invisible rather than wrong.



## OpenAPI

````yaml /openapi.json delete /v1/trips/{trip_id}/days/{day_number}/entries/{entry_id}
openapi: 3.1.0
info:
  title: Stardrift API
  description: >-
    Read and edit the authenticated user's trips, itineraries, recorded
    bookings, and saved lists. Private records are owner-scoped. MCP tool names
    are documented separately from these HTTP operations.
  version: v1
servers:
  - url: https://stardrift.ai/api
security: []
paths:
  /v1/trips/{trip_id}/days/{day_number}/entries/{entry_id}:
    delete:
      tags:
        - mcp-server
      summary: Remove Entry
      description: >-
        Remove one entry from a day — the inverse of add_place / add_day_note.


        The removal is `apply_plan_actions` + `RemoveEntryAction` — the same
        pair

        the LLM edit path uses (`plan/edit_subagent.py`,
        `stream_processing.py`),

        rather than a second implementation of "filter the day's entries". Note
        the

        web does NOT go through this: it removes client-side in

        `lib/plan-mutations.ts` and PUTs the whole plan. What the two share is

        `EditablePlan.save`, which mirrors that PUT's validate-then-save.


        Nothing else is needed here: `item_refs` is a read-time derived index
        that

        `PlanRepository.assemble_content` reconstitutes as `[]` on every load.


        RemoveEntryAction filters, so removing an entry that isn't there
        succeeds

        silently — that would report a deletion which never happened, so a
        missing

        entry_id 404s instead.


        The itinerary activity is deliberately left in place: another day may

        reference it, and an orphaned activity is invisible rather than wrong.
      operationId: >-
        remove_entry_v1_trips__trip_id__days__day_number__entries__entry_id__delete
      parameters:
        - name: entry_id
          in: path
          required: true
          schema:
            type: string
            title: Entry Id
        - name: day_number
          in: path
          required: true
          schema:
            type: integer
            minimum: 1
            title: Day Number
        - name: trip_id
          in: path
          required: true
          schema:
            type: string
            format: uuid
            title: Trip Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RemoveEntryResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
components:
  schemas:
    RemoveEntryResponse:
      properties:
        entry_id:
          type: string
          title: Entry Id
        plan_version:
          type: integer
          title: Plan Version
      type: object
      required:
        - entry_id
        - plan_version
      title: RemoveEntryResponse
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError

````