Frequently Asked Questions (FAQs)

Yes. Through confirmation mechanisms and flow control, Events Hub ensures that events are correctly delivered to recipients.

Events remain available on the Delivery Retry screen for 14 days.

When the first attempt to deliver an event to a subscriber fails, Events Hub tries to automatically resend it, following the settings registered in the policy. If all automatic attempts fail, the event moves to the retry queue on the Delivery Retry screen, where you can manually retry it.

Yes. Through the Event Status API, you can implement automation to automatically resend events from the manual retry queue.

The URL is formed by Base URL + context + handler + topic:

• Base URL: defined by Events Hub. It includes the address of each client's interface + event-receiver + a unique code (hash).

• Context, handler, and topic: created by you. They help organize and manage different publishing channels.

  • Topic is the most specific level.

  • Handlers aggregate topics, serving as a logical grouping layer.

  • Contexts add another grouping level, allowing the same topic to be used in different situations.

If you add policies to your handler, yes. You will need to configure the authorization URL linked to the interceptor. With the exception of "IP Filtering Validation," all depend on this configuration to function.

NOTE

Access the Authorizations documentation to see how to configure them using the Sensedia API Platform.

No. Events Hub accepts any authorization URL to validate event policies.