Skip to content

changes required for pecha api #425

Description

@TenzDelek

pecha endpoint: https://pecha-backend-dev.web.app/swagger/#
we need to list changes required for the pecha api as per the need from the webuddhist backend.

1. issue

will toc create by them?

endpoint related with text

  1. collection / category
    get - /collections

  2. text metadata

- get - /texts
- get - /texts/{text-id}/versions
- get - /texts/{text-id}/contents
- get - /texts/{text-id}/commentatires
- post - /texts/{text-id}/details

  1. text segment

- get - /segments/{segment_id}/info
- get - /segments/{segment_id}/root_text
- get - /segments/{segment_id}/translations
- get - /segments/{segment_id}/commentaries

  1. recitations
    - get - /recitations
    - post - /recitations/{text_id}

  2. search
    -get- /search/multilingual
    -get- /search/chat/{pecha_segment_id}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions