Change Details

**Request Status:** New Request **Request Type:** research and project support **Related OKRs:** Healthy Communications (S2S) **Request Title:** Structured talk APIs -- - **Request Description:** Currently we have two production APIs which parse Talk pages and return a "stuctured" representation of the content as threads and other meta or derived data. This request is to understand the need and potential support to a single API and maintaining and expanding its functionality. - **Indicate Priority Level:**Medium - **Main Requestors:** Josh Minor, Matt Cleinman - **Ideal Delivery Date:** Q4 - **Stakeholders:** Android, iOS, Editing, any external consumers of Talk pages (Enterprise?) **Request Documentation** -- |**Document Type**| **Required?** | **Document/Link** | | **Related PHAB Tickets** | Yes | <add link here> | | **Product One Pager** | Yes |<add link here> | | **Product Requirements Document (PRD)** | Yes | <add link here> | | **Product Roadmap** | No | <add link here> | | **Product Planning/Business Case** | No |<add link here> | | **Product Brief** | No | <add link here> | | **Other Links** | No |<add links here> |

**Request Status:** New Request **Request Type:** research and project support **Related OKRs:** Healthy Communications (S2S) **Request Title:** Structured talk APIs -- - **Request Description:** Currently we have two production APIs which parse Talk pages and return a "structured" representation of the content as threads and other meta or derived data. This request is to understand the need and potential support to a single API and maintaining and expanding functionality, particularly to ensure wide language support. - **Indicate Priority Level:**Medium - **Main Requestors:** Josh Minor, Matt Cleinman - **Ideal Delivery Date:** Q4 - **Stakeholders:** Android, iOS, Editing, any external consumers of Talk pages (Enterprise?) **Request Documentation** -- |**Document Type**| **Required?** | **Document/Link** | | **Related PHAB Tickets** | Yes | <add link here> | | **Product One Pager** | Yes |<add link here> | | **Product Requirements Document (PRD)** | Yes | <add link here> | | **Product Roadmap** | No | <add link here> | | **Product Planning/Business Case** | No |<add link here> | | **Product Brief** | No | <add link here> | | **Other Links** | No |<add links here> |

**Request Status:** New Request **Request Type:** research and project support **Related OKRs:** Healthy Communications (S2S) **Request Title:** Structured talk APIs -- - **Request Description:** Currently we have two production APIs which parse Talk pages and return a "structured" representation of the content as threads and other meta or derived data. This request is to understand the need and potential support to a single API and maintaining and expanding functionality, This request is to understand the need and potential support to a single API and maintaining and expanding its functionalityparticularly to ensure wide language support. - **Indicate Priority Level:**Medium - **Main Requestors:** Josh Minor, Matt Cleinman - **Ideal Delivery Date:** Q4 - **Stakeholders:** Android, iOS, Editing, any external consumers of Talk pages (Enterprise?) **Request Documentation** -- |**Document Type**| **Required?** | **Document/Link** | | **Related PHAB Tickets** | Yes | <add link here> | | **Product One Pager** | Yes |<add link here> | | **Product Requirements Document (PRD)** | Yes | <add link here> | | **Product Roadmap** | No | <add link here> | | **Product Planning/Business Case** | No |<add link here> | | **Product Brief** | No | <add link here> | | **Other Links** | No |<add links here> |