---
title: "Preview JSON-LD"
method: GET
path: "/api/apps/{app_id}/seo/preview/json-ld"
---

# Preview JSON-LD

`GET /api/apps/{app_id}/seo/preview/json-ld`

<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Returns the Schema.org markup Base44 generates from the app's entities, so you can see it before publishing it.

Base44 matches each entity to the Schema.org type its fields look most like, and leaves out any entity it can't match with reasonable confidence, so an app whose entities are all app-specific returns an empty list. Each entry carries the markup as a template: `{field}` placeholders name the entity fields, and Base44 injects the template into the page as it stands rather than filling it in per record.

Nothing here publishes the markup. Save the entries you want as `custom_json_ld` with [Update SEO settings](/api-reference/update-seo-settings), and note that saving is not enough on its own. Base44 injects saved markup only into a page of a search-eligible app, with `seo_disabled` off and `platform_jsonld_injection_enabled` on. Base44 counts an app as search-eligible when it's public. A private or workspace app never is, and an app that requires a login qualifies only where Base44 has turned search indexing on for it. Check all three when markup you saved isn't on the page.

<Warning>Send `confidence` as a string, or leave it out, if you save these entries. The number this endpoint returns is stored as-is, and the copy of your settings that serves the live site can't hold a fractional number, so saving it that way stops that copy updating. Base44's own generator writes `confidence` as a string for the same reason.</Warning>

This endpoint is limited to 30 requests per minute per app, and that budget is shared with the app's other SEO endpoints.

<Warning>The response includes fields beyond the ones documented here. Don't rely on undocumented response fields, as they can change at any time.</Warning>

## Path parameters

- `app_id` string, required — ID of the app.

## Response `200`

The generated Schema.org markup.

- JsonLdPreviewResponse — The preview, wrapped in the field the endpoint returns it under.
  - `result` JsonLdPreview, required — The Schema.org markup Base44 would publish for this app.
    - `entities` JsonLdEntity[] — One entry per entity Base44 could match to a Schema.org type. Empty when none of the app's entities match one confidently.
      - `entity_name` string, required — Name of the app entity this markup describes.
      - `schema_type` string, required — The Schema.org type Base44 matched the entity to.
      - `confidence` number, required — How sure the match is, 0 to 1. Base44 leaves out any entity below 0.2.
      - `json_ld_template` object, required — The JSON-LD Base44 would inject, with `{field}` placeholders naming the entity fields that fill it. Written verbatim into the page, so the placeholders are not substituted per record.
      - `field_mapping` object, required — Which entity field fills each Schema.org property, keyed by property.

## Other responses

- `401` — Missing or invalid credentials.
- `403` — You don't have access to this app, or you used a workspace API key. These endpoints accept a user's credentials only.
- `404` — App not found.
- `429` — Rate limit exceeded (30 requests per minute).

---

[API](https://skmtc.dev/base44/apis/base44-app-management-api.md) · [All operations](https://skmtc.dev/base44/apis/base44-app-management-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/base44/base44-app-management-api/revisions/173e4e9c63c2/schema)