Field-level exposure & PII
Most API tooling stops at “which endpoints.” Elva’s contracts go a level deeper: which fields. Every endpoint in a contract gets a field-by-field exposure decision — on or off, required or optional, constrained or free — with PII and internal-only fields flagged before they can leak into a partner-facing spec or an agent’s tool schema.
This is the step where a contract earns its name. An endpoint list says what consumers can call; the field list says exactly what they will see.
The field table
The Schema step groups your selected endpoints by service — an identity service here, an inventory API there — with each endpoint showing its exposure count at a glance ( 2/2 Fields, 12/15 Fields ). Expand one and every field becomes a row you control:
Column | What you control |
Include checkbox | Whether the field exists in this contract at all — unchecked fields vanish from every generated artifact |
Field & badges | The field name, flagged with PII or Internal when it carries sensitive or non-public data |
Type | The field's data type, editable from a dropdown |
Value | An example value consumers and agents will see in the generated spec and docs |
Description | Human-and-model-readable meaning ("User's primary email address") |
More | Mark the field required or add constraints |
Bulk decisions in one click
Nobody wants to toggle 58 checkboxes by hand. Quick actions apply a policy across the whole contract — or, with the “This endpoint only” variant, to a single endpoint, with Restore defaults as the undo:
- Include all — start from full exposure and trim down.
- Required only — expose the minimal viable surface.
- Exclude PII — drop every flagged personal-data field at once.
- Exclude internal — drop everything marked internal-only.
A search fields box gets you to any field in a large contract instantly, and the AI assistant does the same work conversationally — “mark every ID required and exclude all PII” is a sentence, not a session.
The tally that keeps you honest
The wizard footer carries two numbers everywhere you go: Exposed fields (say, 49/58) and a warning-colored PII Exposed count. If the contract ships with 18 PII fields exposed, that happened in full view — not as a surprise in a security review six months later.
Every artifact inherits these decisions. A field you exclude here is absent from the hosted spec, the docs, the SDK types, the Postman collection, and the MCP tools agents call. There is no second copy to forget.
This is data governance where it belongs — at contract time, not incident-review time. The moment of exposure is the moment of decision, and the decision is one click.
Where to go next
Publishing targets
Where the trimmed, governed surface materializes: spec, docs, MCP server, SDKs, and tooling.
Governance & stakeholders
Breaking-change policy, validation rules, and who signs off before a publish.
On this page
- Field-level exposure & PII