# Documenting REST and probably FHIR end-points

**URL:** <https://talk.openmrs.org/t/documenting-rest-and-probably-fhir-end-points/27473>\
**Category:** Development\
**Tags:** fhir, documentation, rest\
**Created:** [March 18, 2020, 8:38am UTC](https://talk.openmrs.org/t/documenting-rest-and-probably-fhir-end-points/27473 "2020-03-18T08:38:30Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jennifer](https://talk.openmrs.org/user_avatar/talk.openmrs.org/jennifer/32/8531_2.png) [@jennifer](https://talk.openmrs.org/u/jennifer)\
**Post date:** [August 25, 2022, 5:55pm UTC](https://talk.openmrs.org/t/documenting-rest-and-probably-fhir-end-points/27473/4 "2022-08-25T17:55:37Z")

</div>

> [@ibacher](#):
>
> @grace Having solid docs for the REST API is a very important consideration for DevX, especially with O3. I don’t know if there’s a way we can strategise to try and make this documentation better and part of the usual effore.

@ibacher It’s like you read my mind! While it was great having a dedicated technical writer working on the [REST API documentation through Google Season of Docs 2019](https://talk.openmrs.org/t/gsod-2019-improved-rest-api-documentation/24328), that effort ended with the end of GSoD2019. This could be so much more sustainable if we can work documentation into our process and share the responsibility.

---

_[View the full topic](https://talk.openmrs.org/t/documenting-rest-and-probably-fhir-end-points/27473)._