The Responses API is part of Typeform's standard API and works for forms on any plan that allows API access. Some Typeform plan limits apply, rate limits on the API and retention windows for very old responses. SleekView caches responses on first pull, so once cached they remain available locally even if Typeform's retention purges them remotely.

SleekView doesn't change how you embed Typeforms (Embed SDK, iframe, or popup). It connects via your Typeform Personal Access Token, lists your forms, and lets you pick which to sync into the local cache. The embed and the sync are independent, sync continues even if you remove an embed from a page.

Yes. Hidden fields are part of the response payload from the Responses API, surfaced as hidden object members per response. SleekView reads the keys actually present across recent responses and exposes them as addable columns. New hidden field names appear after the next sync that contains them.

Not by default. Typeform's API supports response edit operations only in narrow cases, and pushing edits from WordPress would risk diverging the source of truth. SleekView is read-only against Typeform; local triage tags live in WordPress and never sync back. If you need round-trip editing, the Typeform UI remains the right surface for that.

Sync interval is configurable per form (5 minutes, 15 minutes, hourly, daily). The Responses API supports incremental fetch by submitted-at, so each run only pulls new responses. Manual refresh from the SleekView toolbar forces an immediate pull when you need fresher data than the schedule provides.

Calculator variables appear in the response payload as variables; SleekView pivots them into columns the same way it does hidden fields. Logic-jump branching is reflected in which questions have answers in a given response, questions skipped by logic simply have no answer for that response, and SleekView shows those cells as blank.

The cached row in WordPress remains until you choose to purge. SleekView surfaces a tombstone state on the row when the next sync confirms it's gone from Typeform. Useful for retaining audit trails when a response was acted on locally before deletion. Bulk purge is available when you want the local cache to mirror Typeform exactly.

Yes. Each Typeform account connects with its own Personal Access Token. SleekView stores each connection separately and lets you tag forms with the source account, so a multi-brand site can keep brand-A and brand-B Typeform responses in separate views or unified into one cross-account view depending on the workflow.