Get thank-you page by id

Entry identifier. Strapi 5 prefers documentId (string) for GET /api/{type}/{id}; numeric id may return 404. The Nuxt app usually queries collections with ?filters[id][$eq]=… or ?filters[slug][$eq]=… instead.

Restrict returned attributes. Indexed array syntax: ?fields[0]=slug&fields[1]=title.

Populate relations, media, components, and dynamic zones. See Strapi 5 populate.

Strapi 5 (supported)

• One level: ?populate=* or ?populate[0]=cover_image&populate[1]=author.
• Nested: ?populate[author][populate][avatar]=true (use =true, not =*, on components).
• Dynamic zones: ?populate[content][on][sections.hero][populate][image]=true.
• Field selection: ?populate[seo][fields][0]=metaTitle alongside nested populate.

Deep populate (strapi-v5-plugin-populate-deep)

• Native: ?pLevel or ?pLevel=5 (default depth 5).
• Legacy (frontend): ?populate=deep or ?populate=deep,N — mapped to pLevel by backend middleware.

Not supported on Strapi 5 (v4-only; returns 400)

• Comma lists: ?populate[content][populate][0]=items.media,CTA,cta,….
• Dot paths with field picks: ?populate[7]=banners.bottom_banner.image.url, ?populate[3]=author.avatar.
• populate[relation]=* on some components (use explicit nested keys).

Frontend query builders (canonical S5 strings): website-frontend/utils/strapi-populate/ — getCompetitorPopulateParams(), getTemplatePopulateParams(), getArticlePopulateParams(), etc.

Prefer explicit populate over deep/pLevel when possible; deep queries are heavier.

Strapi i18n locale code. The Whatagraph backend currently serves English content only.