Developers and API
Is there an API and are there SDKs?
Yes. Every content type defined in the schema builder is readable over the API the moment it exists, with no endpoint to write by hand. SDKs wrap the same API for the common frameworks. API keys are issued per project and the key is shown once at creation, so a leaked key is replaced rather than recovered.
No endpoint to write
Define a type in the schema builder and it is readable over the API the moment it exists. There is no controller to add, no route to register and no deploy in between. Adding a field on Tuesday morning means it is queryable on Tuesday morning.
This is the property that makes a schema change cheap, and cheap schema changes are why the model can stay honest instead of accumulating a field called extra text.
Keys are per project and shown once
A key belongs to one project, so a key that escapes cannot read another project in the same workspace. It is displayed once at creation and never again.
That is deliberate. A key you can look up later is a key that lives in the interface as well as in your secret store, which doubles the number of places it can leak from.
If a key leaks, replace it
There is no recovery path and there should not be one. Create a new key, deploy it, delete the old one. Because keys are scoped to a project, the blast radius of that mistake is one site rather than the account.
Also in developers and api
Still have a question left
Thirty minutes with the product team, and a straight answer.