API

This page describes the availability and scope of application programming interfaces (APIs) provided by Probativa.

Probativa APIs are intended to support controlled integration, automation, and operational workflows where appropriate.

API Philosophy

Probativa approaches APIs with the same principles applied to its software products:

  • Purpose-driven
    • APIs exist to support specific, well-defined use cases, not to expose unnecessary surface area.
  • Security-conscious
    • API access is designed to minimize risk and avoid unintended data exposure.
  • Operational clarity
    • API behavior is predictable, documented, and suitable for professional environments.
  • Stability over novelty
    • Changes are introduced carefully to preserve compatibility.

Availability

API availability depends on the product and deployment context.

  • Some Probativa products may not expose public APIs
  • Where APIs are available, they are provided for explicitly supported use cases
  • APIs are not guaranteed to be available across all products or versions

If API access is required for your use case, please contact us to discuss availability and suitability.

Typical Use Cases

Where provided, Probativa APIs may support scenarios such as:

  • Integration with internal systems
  • Automation of operational workflows
  • Retrieval of status or execution results
  • Controlled interaction with licensing or management functions

APIs are designed to complement, not replace, existing product functionality.

Authentication and Access Control

API access is subject to appropriate access controls.

Depending on the product and implementation, this may include:

  • Authentication mechanisms suitable for the environment
  • Scoped or limited permissions
  • Separation between operational and administrative actions

API credentials must be handled securely by customers.

Data Handling

APIs are designed with data minimization in mind:

  • Only required data is exposed
  • No unnecessary personal data is transmitted
  • Data returned is limited to the scope of the request

For information on personal data processing, refer to the Privacy Policy and Compliance & GDPR pages.

Versioning and Compatibility

Where APIs are provided:

  • Interfaces are versioned where appropriate
  • Backward compatibility is maintained whenever possible
  • Changes that affect compatibility are communicated in advance when feasible

Customers are responsible for maintaining compatibility with supported API versions.

Documentation

API documentation, where available, includes:

  • Supported endpoints and operations
  • Request and response formats
  • Authentication requirements
  • Usage constraints

Documentation may be provided:

  • As part of product documentation
  • Upon request for enterprise customers
  • As part of a commercial or support agreement

Limitations

Probativa APIs:

  • Are not intended for unrestricted public use
  • May be subject to usage limits or contractual terms
  • Do not imply a commitment to expose all internal functionality

Probativa does not guarantee API availability beyond documented and supported use cases.

Enterprise Integration

Organizations requiring:

  • Custom integrations
  • API access for regulated environments
  • Long-term integration stability
  • Documentation suitable for internal review

are encouraged to contact us to discuss requirements.

Contact

If you are interested in API access or need clarification about integration options, please contact us.

We aim to provide clear guidance on what is supported and appropriate.