Skip to main content

Store Service History in Core

Procivis One can record a history of API events from all server components, storing them centrally in Core. This provides a record of system activity across your deployment.

Prerequisites​

  • Core must be deployed and accessible to other services

Configuration​

1. Enable the history endpoint in Core​

In your Core configuration, set:

app:
  enableHistoryEndpoint: true

This enables the POST /api/history/v1 endpoint that other services use to push history events.

2. Configure each service to push history​

For each server component, add the following to its configuration:

history:
  type: REMOTE_REST
  enabled: true

Configure this for:

  • Enterprise Backend (one-frontend-backend)
  • Bridge (one-bridge)
  • Wallet-Relying Party Registry (one-wallet-relying-party-registry)
note

History is only recorded for services where history.enabled is set to true.

User attribution​

If you are using STS authentication, history entries include a user field identifying who triggered the event. In other authentication modes this field is not populated.

Retrieving history​

Once enabled, you can query stored events using:

  • GET /api/history/v1 — list history events (supports filtering)
  • GET /api/history/v1/{id} — retrieve a specific event

For filtering options and query parameters, see History.

How it works​

When a service receives an API request, it forwards event details to Core's history endpoint.

  • If using STS authentication: The service authenticates using an STS token with the HISTORY_CREATE permission.
  • If using any other authentication mode: No permission is checked.

Core stores the event in its database, making it available for later retrieval and audit purposes.