# API: Metadata too large to include in endpoints? **URL:** \ **Category:** Technical\ **Tags:** api\ **Created:** [April 1, 2023, 12:32am UTC](https://forum.openreferral.org/t/api-metadata-too-large-to-include-in-endpoints/378 "2023-04-01T00:32:44Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![timothyhinh](https://avatars.discourse-cdn.com/v4/letter/t/e8c25b/32.png) [@timothyhinh](https://forum.openreferral.org/u/timothyhinh)\ **Post date:** [April 1, 2023, 12:32am UTC](https://forum.openreferral.org/t/api-metadata-too-large-to-include-in-endpoints/378/1 "2023-04-01T00:32:44Z")
Hello @devin @davidraznick ! The HSDS schema includes metadata for each object. But is this strictly necessary to include in the response for the API endpoints (e.g. services, service\_at\_locations, etc.) to be HSDS-compliant? Considering the deeply nested structure of an endpoint like /services (which includes other objects like organization, phones, service\_areas, etc.), how frequently each object could be updated, and the field-level granularity of metadata, this would add an impractical amount of data for each service object returned. ---
**Author:** ![timothyhinh](https://avatars.discourse-cdn.com/v4/letter/t/e8c25b/32.png) [@timothyhinh](https://forum.openreferral.org/u/timothyhinh)\ **Post date:** [April 1, 2023, 12:34am UTC](https://forum.openreferral.org/t/api-metadata-too-large-to-include-in-endpoints/378/2 "2023-04-01T00:34:37Z")
Tagging @skyleryoung ---
**Author:** ![davidraznick](https://avatars.discourse-cdn.com/v4/letter/d/85f322/32.png) [@davidraznick](https://forum.openreferral.org/u/davidraznick)\ **Post date:** [April 2, 2023, 7:51pm UTC](https://forum.openreferral.org/t/api-metadata-too-large-to-include-in-endpoints/378/3 "2023-04-02T19:51:58Z")
Agreed, adding metadata is definitely optional, it is up to the publisher if they provide it or not in each request. We should make that explicitly clear.