API and integration
Our API is treated as a fully fledged product: version management, documentation, notice periods for changes and an explicit access policy. Those who build on our infrastructure must be able to rely on it.
The API as a full product
Those who build on our infrastructure must be able to rely on it. Reliability toward third parties is the same promise as toward the professional.
Version control
Changes are managed and predictable; existing integrations do not break without notice.
Documentation
The integration is documented, so that an integration is traceable and maintainable.
Notice periods
We announce changes in advance, with a reasonable period to adapt.
Explicit access policy
Access is deliberate and bounded; who has access to what is recorded.
The honesty rule
Our platform is connected via the API to an existing external ecosystem. Its users are not customers of Velvet.red and are nowhere counted or presented by us as such. A company that sells trust and dresses up its figures with other people's users has already broken its product; that is why you will not find this here.
The honesty rule is also enforced technically: metrics on our own users and on ecosystem traffic are separated at the architecture level. What may not be added together does not sit in the same table.
Request the integration documentation through an introductory conversation.