Reference

API

There is no public API yet. This page says what that means, so nobody plans around something that does not exist.

Status

No endpoints, no keys, no client library. API access appears on the Business plan as a capability in our plan configuration, and there is nothing behind it to call. Nothing on this page is available today.

What does exist

A published view is a URL. If what you want is the page, you already have the integration: send the link or embed it. A gated view will ask a person for a password or an email confirmation, which is the point of a gate and is not something a script gets around.

Everything else is done in the dashboard: connecting a workspace, choosing a source, switching attributes on, setting an access policy, publishing, approving a pending edit, and forcing a check with Sync now.

What we would build first

In this order, because it is the order people have asked in. Nothing here is a commitment and none of it has a date.

Read the records behind one of your own views, with the same projection a viewer gets.
List your views, with their status, source, and the time each last updated.
Trigger a check on a source, the same thing Sync now does, with the same rate limit.
Read the pending edit queue, and approve or reject an edit.
Export the per-viewer access log that Business already keeps.

Two constraints are already decided, whatever the endpoints turn out to be. It will be a publisher API, authenticated as you and scoped to your workspace, never a viewer API. And it will not become a way to read attributes a view does not publish, because that would make the projection rule on the security page a statement about the web page rather than a statement about the product.

If you need one

Tell us what you would call and what you would do with the result. An API built from three real requests is better than one built from a guess, and the request also tells us whether to build it before or after the things on the roadmap. Write to help@publicviews.app.