Test Callback Endpoint

post

/v1/besu/event-subscriptions/test-callback

Use this to verify delivery to an HTTPS callback URL without creating a subscription. It optionally supports OAuth, TLS, and a custom JSON payload.

Request

There are no request parameters for this operation.

Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Request to test delivery to an event subscription callback endpoint.
Show Source
Nested Schema : EventSubscriptionOAuthConfig
Type: object
OAuth 2.0 configuration for callback authentication.
Show Source
  • Default Value: true
    Controls OAuth token request client-auth placement. When true, sends `clientId:clientSecret` in an HTTP Basic Authorization header to the token endpoint. When false, sends client_id and client_secret form fields in the token request body.
  • OAuth 2.0 client identifier registered for the callback endpoint.
  • OAuth 2.0 client secret used for token acquisition.
  • Default Value: client_credentials
    Allowed Values: [ "client_credentials", "refresh_token" ]
    OAuth 2.0 token grant used for callback access-token acquisition. client_credentials obtains an access token with the configured client credentials. refresh_token uses the supplied refreshToken and retains any replacement refresh token returned by the identity provider.
  • Required when grantType=refresh_token; pre-provisioned OAuth refresh token used to mint callback access tokens.
  • Space-delimited OAuth scopes requested during token exchange.
  • EventSubscriptionTlsConfig
    TLS or mTLS configuration for callback delivery. If mTLS is used, both clientCert and clientKey must be provided together.
  • EventSubscriptionTlsConfig
    TLS or mTLS configuration for callback delivery. If mTLS is used, both clientCert and clientKey must be provided together.
  • OAuth 2.0 token endpoint used to obtain access tokens for callbacks.
Match All
OAuth 2.0 configuration for callback authentication.
Show Source
Nested Schema : EventSubscriptionTlsConfig
Type: object
TLS or mTLS configuration for callback delivery. If mTLS is used, both clientCert and clientKey must be provided together.
Show Source
Examples

Back to Top

Response

Supported Media Types

204 Response

Returns confirmation that callback delivery succeeded.

400 Response

Validation failed.
Body ()
Root Schema : ErrorResponse
Type: object
Error response returned by the service.
Show Source
Nested Schema : upstreamError
Type: object
Additional Properties Allowed: true
Complete error object returned by the Besu node, including code, message, and data fields, when available.
Examples

500 Response

Unexpected service error.
Body ()
Root Schema : ErrorResponse
Type: object
Error response returned by the service.
Show Source
Nested Schema : upstreamError
Type: object
Additional Properties Allowed: true
Complete error object returned by the Besu node, including code, message, and data fields, when available.
Examples

503 Response

Event subscriptions are unavailable.
Body ()
Root Schema : ErrorResponse
Type: object
Error response returned by the service.
Show Source
Nested Schema : upstreamError
Type: object
Additional Properties Allowed: true
Complete error object returned by the Besu node, including code, message, and data fields, when available.
Examples

Back to Top