Backoffice API
    Backoffice API
    • Back to home
    • Magazines
    • Issues
      • List Issues by Workspace id
        GET
      • Create Issue in Workspace
        POST
      • Issue by id
        GET
      • Update Issue by id
        PATCH
      • Delete Issue by id
        DELETE
      • Restore soft deleted Issue by id
        POST
    • Sections
      • All sections by Issue id
        GET
      • Create Section in Issue
        POST
      • Section by id
        GET
      • Update Section by id
        PATCH
      • Remove Section by id
        DELETE
    • Blocks
      • All blocks by Section id
        GET
      • Bulk update blocks by Section id
        PUT
      • Block by id
        GET
      • Update Block by id
        PATCH
    • Slots
      • All slots by Block id
        GET
      • Bulk update slots by Block id
        PUT
    • SectionContents
      • List SectionContents by Issue id
        GET
      • Search SectionContents by Issue id
        GET
      • Create SectionContent in Section
        POST
      • Remove SectionContent by id
        DELETE

    Magazines

    Entity deletion#

    In Omerlo APIs, you see three kind of endpoints regarding entity deletion:
    delete: this represent a soft deletion meaning the data won't be removed completely. In background, we just tag the entity as deleted setting a datetime value to the common deleted_at field.
    Specificity: always a DELETE http method that ends with a uuid.
    restore: endpoint that aims to set deleted_at datetime value to null, restoring the given entity to NOT deleted.
    Specificity: always a POST http method that ends with a uuid/restore.
    remove: permanently destroy the targetted entity. It won't be available anymore.
    Specificity: always a DELETE http method that ends with a uuid/remove.
    Please not that a soft deleted entity won't be available anymore in ReaderAPI.
    Modified at 2025-05-28 08:41:51
    Built with