# How OSLC make REST API self descriptive?

**URL:** <https://forum.open-services.net/t/how-oslc-make-rest-api-self-descriptive/628>\
**Category:** OSLC\
**Created:** [May 31, 2022, 8:52am UTC](https://forum.open-services.net/t/how-oslc-make-rest-api-self-descriptive/628 "2022-05-31T08:52:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![talhashahid009](https://forum.open-services.net/user_avatar/forum.open-services.net/talhashahid009/32/198_2.png) [@talhashahid009](https://forum.open-services.net/u/talhashahid009)\
**Post date:** [May 31, 2022, 8:52am UTC](https://forum.open-services.net/t/how-oslc-make-rest-api-self-descriptive/628/1 "2022-05-31T08:52:52Z")

</div>

As mentioned the benefits of OSLC are that it makes REST API self-descriptive. How?

Because every REST API is different from others.

Can you please elaborate on this point or guide me to some good reading?

Thanks!..

---

<div class="post-metadata">

**Author:** ![isccarrasco](https://forum.open-services.net/user_avatar/forum.open-services.net/isccarrasco/32/220_2.png) [@isccarrasco](https://forum.open-services.net/u/isccarrasco)\
**Post date:** [June 11, 2022, 8:44pm UTC](https://forum.open-services.net/t/how-oslc-make-rest-api-self-descriptive/628/2 "2022-06-11T20:44:30Z")

</div>

Hello @talhashahid009  
The documentation of the OSLC spec could be a good starting point for you I believe.

What I have learned of self-descriptive of a REST API by implementing OSLC is about the implementation of a specific endpoint which is an entry point (ServiceProviderCatalog) and contains the definition of the services (service providers) and resource shapes that you can use to interact with the resources of an application.

You could go deep on this concepts [here](https://docs.oasis-open-projects.org/oslc-op/core/v3.0/os/oslc-core.html).

Regards!