# 3.5. Interfaces, APIs and client modules (TECHNOLOGY)

**URL:** <https://discourse.gbif.org/t/3-5-interfaces-apis-and-client-modules-technology/1973>\
**Category:** Collections Catalogue\
**Created:** [March 27, 2020, 10:45am UTC](https://discourse.gbif.org/t/3-5-interfaces-apis-and-client-modules-technology/1973 "2020-03-27T10:45:02Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![waddink](https://sea1.discourse-cdn.com/gbif1/user_avatar/discourse.gbif.org/waddink/32/333_2.png) [@waddink](https://discourse.gbif.org/u/waddink)\
**Post date:** [April 23, 2020, 8:02pm UTC](https://discourse.gbif.org/t/3-5-interfaces-apis-and-client-modules-technology/1973/7 "2020-04-23T20:02:51Z")

</div>

The mockups for the catalog, although visually appealing, seem to distract me a little from the use cases that indicate that an api and machine actionable metadata might me more important than a human browsable listing of collections. For instance the need to use collections descriptions in a service like ELViS. Also they do not show anything about possible operations, metadata, standards, update mechanisms, provenance etc.

---

_[View the full topic](https://discourse.gbif.org/t/3-5-interfaces-apis-and-client-modules-technology/1973)._