Event | Description |
|---|---|
Realm |
|
Channel | A channel exchanges data between integrated applications. |
Publisher | A publisher pushes data to a channel as an application, service, or system. |
Publisher component | The Transit Hub team's library that enables the application to publish data. |
Schema | The publisher writes a schema that serves as a contract detailing the data they will publish to a channel. Publishers can offer multiple schemas on the same channel, such as one for creating, one for updating, and one for deleting. The system validates each published message against the corresponding schema. |
Subscriber | A subscriber receives data from a channel as an application, service, or system. |
Subscriber component | The Transit Hub team's library that enables the application to receive data. |
Event | A payload unit that carries data across a channel. |
Action | Activities that can take place independently within the concept, such as starting and completing e-filing. |
Customer | ¶¶Òõ³ÉÄê’ customers |
Client | A firm's customer |
Webhook | Endpoints registered to a channel, such as the customer e-filing HTTPS callback. |