Skip to content

POST /v1/bookmarks requires undocumented 'lastMutationAt' field #73

@sharabash

Description

@sharabash

Summary

The POST /v1/bookmarks endpoint returns 422 Unprocessable Entity with the message "lastMutationAt" is required, but this field is not documented in the Add user bookmark API docs.

Observed behavior

Request:

{
  "key": 2,
  "type": "ayah",
  "verseNumber": 255,
  "mushaf": 4
}

Response: 422 Unprocessable Entity

{
  "message": "\"lastMutationAt\" is required",
  "type": "unprocessable_entity",
  "success": false
}

Expected behavior

Either:

  1. The lastMutationAt field should be documented (type, format, and purpose), or
  2. The field should be optional with a server-side default if not provided

Context

The documented request body schema (add-user-bookmark.api.mdx) lists only key, type, verseNumber, isReading, and mushaf as fields. The lastMutationAt field is not mentioned anywhere in the docs.

Tested against: https://apis-prelive.quran.foundation/auth/v1/bookmarks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions