API interfaces
Define request shapes, responses and permission requirements.
Products · Systems & runtime
Service contracts
Service contracts describe how applications exchange requests, events and data across a system boundary.
For: Teams coordinating APIs, integrations and independently maintained services.
Overview
Make system interactions explicit.
A service contract captures what a caller can send, what it receives and how failures are represented. Record permissions, compatibility and change expectations alongside the interface so producers and consumers can evolve together.
Possible use cases
Use cases for Service contracts.
Event schemas
Describe the meaning and structure of messages between systems.
Integration agreements
Align teams on ownership, compatibility and failure expectations.
Plan the right scope
What to bring to the discussion.
- Producers, consumers and interface ownership
- Schemas, errors and backward compatibility
- Authentication, versioning and contract validation
More in systems & runtime.
Your next step
Explore Service contracts for your workflow.
Share your users, existing systems and intended outcome. We can map the requirement to a suitable product direction or engineering scope.