Response objects

The five platforms are five different systems. A place has opening hours and a price level; a video has a sound and a duet setting; a LinkedIn profile has experience and education; a post on X has the post it answers. Forcing them into one “profile” and one “post” would hide exactly the fields you came for, so we don’t. Each object is named after the platform’s own developer API where one describes the same thing — if you have read those docs, you already know these fields:

• Google Maps: named after Google's Places API.
• LinkedIn: named after the words LinkedIn prints, since LinkedIn has no official data API.
• Instagram: named after Instagram's Graph API.
• TikTok: named after TikTok's Display and Research APIs.
• X: named after X's API v2.

What is the same everywhere

The conventions, not the shapes. The { data, meta } envelope and the error format. snake_case keys. Timestamps as ISO 8601 in UTC. The platform’s own ids, as strings, so you can join them to anything else you hold. Counts as integers.

Every key, every time. An object carries every field its page lists, on every call. A field is null when the platform does not show it — never 0, never a guess — and a list is empty rather than missing. You can index into a response without checking whether a key exists.

Nothing else. The fields on these pages are an allowlist the gateway enforces: anything not on it is dropped before a response leaves, so a field never appears that is not documented.