Design Principles

Our goal is to make our API integration experience straightforward. When we make decisions, we anchor around the following:

• Our dashboard and internal tools use the same APIs as you, helping us catch problems early and ensure the API is complete
• Domain specific. We aim to make our API straightforward, building constructs around the problems that Bridge is solving
• Consistency. whether it’s naming conventions, types or errors
• Backward compatibility. We try out very best to limit any breaking changes, or require any work in your code to maintain compatibility
• Forward compatibility. We may add new features, but prioritize an interface that allows future expansion without change