LogoLogo
EDCDSPortalDAPS
CE 11.0.0
CE 11.0.0
  • Welcome
  • Key Concepts
  • FAQ
  • Frontend
    • Walkthrough
    • Dashboard
    • Providing
      • 1. Create Data Offer
      • 2. Create Asset
      • 3. Create Policy
      • 4. Create Contract Definition
    • Consuming
      • 1. Finding Offers
      • 2. Initiating Transfers (HttpData-Push)
      • 3. Transfer History
    • Contract Termination
  • Backend
    • Postman
    • API-Wrapper vs Management-API
    • API-Wrapper
      • Java Client Library
    • Management-API
      • Secrets API
      • Contract Definition: Multiple Assets
      • QuerySpec
      • Health Check APIs
      • Policy: Business Partner Groups
      • Policy: Unrestricted
    • Data Transfer
      • HttpData-Pull (Parameterized)
      • AWS S3 Transfer
      • Source: Audit Headers
      • Source/Sink: OAuth2/API-Key
  • Community Edition Deployment
    • Overview
    • Local Demo
    • Production
  • Customer Links
    • Glossary
    • sovity Hub
    • Service Desk
Powered by GitBook
LogoLogo

sovity

  • Homepage
  • About us
  • GitHub
  • LinkedIn

Information

  • Contact
  • Imprint
  • Privacy Policy

© by sovity GmbH

On this page
  • Health Checks for Your Connectors
  • Conclusion

Was this helpful?

Edit on GitHub
  1. Backend
  2. Management-API

Health Check APIs

Health Checks for Your Connectors

In this article, we describe the recommended APIs for performing health checks on your connectors from the outside of a cluster. These APIs ensure the connectivity and functionality of your services and connected core-services by returning status codes and relevant statistics.

General API Accessibility

For a basic health check that should always return a 200 OK status and provide statistics about the connector, use the following API:

  • Endpoint: GET {{Management-API}}/wrapper/ui/pages/dashboard-page

  • Description: This API belongs to the API-Wrapper, which also provides connector statistics and details for the UI dashboard.

Testing interaction with the Dataspace IAM

To test the interaction with the Dataspace IAM (MIW, DAPS, DIM, ...), it is recommended to use the catalog request of your own connector. The Dataspace IAM is integrated into this flow for the DSP message. The body of the request can have a limit set to 1 and should also return a 200 OK status.

  • Endpoint: POST {{Management-API}}/v3/catalog/request

  • Request Body: Please refer to the latest Postman collection for up-to-date details on the request body.

Conclusion

By using these APIs, you can perform effective health checks and ensure the proper functionality and interaction of your connectors within the system. If you have further questions or need additional support, please refer to our documentation or contact our support team.

Last updated 2 months ago

Was this helpful?