--- title: "API Delivery, GraphQL & Assets" description: "Solve common API issues such as missing referenced entries, asset metadata errors, GraphQL locale mismatches, and 422 reference limits." url: "https://www.contentstack.com/docs/headless-cms/api-delivery-graphql-assets" product: "Contentstack" doc_type: "guide" audience: - developers - admins version: "current" last_updated: "2026-05-11" --- # API Delivery, GraphQL & Assets ## 1\. Referenced Entries Not Included in CDA Response Referenced entry fields or names do not appear in the Content Delivery API (CDA) response when fetching entries. **Root cause** The Delivery API does not automatically expand reference fields. Referenced entries must be explicitly included using the appropriate inclusion parameters. Common causes include: * Missing include\[\] parameter in REST (CDA) requests * Missing nested reference selection in GraphQL queries * Referenced entries not published in the requested environment * Locale mismatch between the parent and referenced entry If inclusion is not configured correctly, only the reference UID is returned. **Resolution** For REST (CDA): * Use the include\[\] parameter to expand referenced fields. * Specify include\_depth if nested references are required. For GraphQL: * Explicitly query nested reference fields in the selection set. Additionally: * Confirm referenced entries are published. * Verify environment and locale alignment. Re-run the request with proper inclusion parameters and confirm that referenced entry fields are expanded in the API response. * * * ## 2\. Missing referenced entry details in API responses Retrieving content via the API may return incomplete data for referenced entries even when include parameters are used. This prevents developers from accessing nested or linked content within a single request. **Root cause** The include\_all configuration is not enabled for the specific stack, limiting the ability to retrieve all referenced details. **Resolution** 1. Enable the include\_all feature for the stack settings to allow full reference retrieval. 2. Ensure the API request parameters explicitly specify the references to be included. After the include\_all feature is enabled, execute the API request for an entry with references. If the JSON response contains the full details of the referenced entries, the feature is active. * * * ## 3\. Asset Metadata (Dimensions) Missing in API Response Image width and height values are not included in the Delivery API response, even though they appear in the UI. **Root cause** The Delivery API does not return asset dimensions by default to optimize response size. The include\_dimension=true query parameter must be explicitly provided. **Resolution** * Add include\_dimension=true to the Delivery API request. * Re-fetch the entry or asset. The API response includes width and height under the asset metadata. * * * ## 4\. CDA 422 Error Due to Reference Resolution Limit (100) A Delivery API request fails with a 422 Unprocessable Entity error indicating that the number of resolved references exceeds the allowed limit. **Root cause** The Content Delivery API enforces a strict maximum of 100 resolved references per request, including nested references. When the total number of expanded references exceeds this limit, the API returns a 422 validation error. This commonly occurs when: * Using include\_all=true * Using high include\_depth values * Querying entries with deeply nested reference structures **Resolution** * Reduce include\_depth where possible. * Avoid include\_all unless necessary. * Split large requests into multiple smaller requests. * Merge results client-side if needed. After reducing reference expansion, the API request completes successfully without triggering the 422 error. * * * ## 5\. Missing fields in REST API entry response Retrieving content via the REST API may return incomplete data when querying an older version of an entry. This prevents viewing fields like overview or table\_of\_contents that are visible in the Entry UI. **Root cause** The requested entry version does not contain the specific fields added in later versions of the content. **Resolution** 1. Verify the version number of the entry being requested in the API call. 2. Query the latest version of the entry to ensure all fields are included in the response. 3. Compare the API output against the Entry UI to identify version discrepancies. After updating the API request to target the latest version, execute the GET request. If the missing fields appear in the response, the content is correctly synchronized. * * * ## 6\. Missing tags in Delivery API locale responses Querying entry data for specific locales via the Delivery API may result in missing tag fields. This prevents localized content from displaying tags that have been added to the latest version of the entry. **Root cause** The API request is targeting an older version of the entry that was saved before the tags or fields were implemented. **Resolution** 1. Navigate to the Entry UI and verify the latest version number for the affected locale. 2. Update the Delivery API query parameters to target the latest version of the entry. 3. Ensure the fields exist in the specific version being requested. After adjusting the query to the latest version, perform a new API call for the affected locale. If the tags appear in the JSON response, the data discrepancy is resolved. * * * ## 7\. GraphQL returns master content despite fallback\_locale being disabled Querying entries via GraphQL may return master locale content even if the fallback\_locale parameter is set to false. This prevents users from receiving an empty response or error when content does not exist in the requested locale. **Root cause** The entry exists and is published in the master locale but has not been localized for the specific language being requested in the query. **Resolution** 1. Localize the entry for the specific target language within the CMS. 2. Publish the localized version of the entry to the desired environment. 3. Ensure the query targets the correct locale where the localized content resides. After localizing and publishing the entry, execute the GraphQL query again with fallback\_locale: false. If the localized content appears instead of the master locale data, the configuration is correct. * * * ## 8\. Resolving slow stack performance caused by large assets Managing entries in the stack may experience significant delays and slow response times when the stack contains very large assets. This prevents efficient content management and increases API response latency. **Root cause** Extremely large asset sizes, ranging from 100MB to 1.5GB, are causing high response times during delivery operations. **Resolution** 1. Review CDA logs to identify specific assets causing high latency. 2. Reduce the file size of assets currently stored in the stack. 3. Implement caching strategies to decrease the load on the origin server. After optimizing asset sizes and implementing caching, monitor the stack response times in the logs. If the response times return to normal operating levels, the performance bottleneck is cleared.