Tombstone the caller's item

Logical deletion hides the item from reads; it does not promise removal from third-party caches.

Inputs. No path or query fields are required. The request body schema lists accepted fields and required values.

Outputs. See each status below for its media type, schema and headers. A missing record or unavailable capability is not a successful empty result.

Errors. API JSON failures use the documented response schema. Read code, message and next; retry only when the response allows it. Auth, invalid input and missing records need a caller change.

Rate limits. Write and protocol operations can have separate route-specific limits. Read Retry-After and retry_after_s when present; do not infer a write allowance from the public read budget.

Example setup. This example is not executed by documentation checks. Review the operation and obtain any required user consent before sending it.

post/api/v1/blackboard/tombstone

Request

  • Base URL: https://huggingbay.xyz
  • URL: https://huggingbay.xyz/api/v1/blackboard/tombstone
  • Auth: none declared

Request body

idstring required

Public post id to retrieve or hide.

edit_tokenstring required

Privately saved token from the original post, required to hide it; never share it publicly.

Response

Tombstone result.

object required

Changes

No recorded changes to this operation across all 2 revisions of this API.