🏛 Architecture

Here is a diagram describing the implementation.
Firebase architecture
Firebase architecture

🔚 Endpoints to link and unlink tokens

As described in the diagram above, we will need you to send the firebase token/tokens to these endpoints below when it gets linked/unlinked to a user. You can also publish messages on the RabbitMQ with the specified notification type.
REST API
RabbitMQ Connector
Kafka Connector

⬆️ POST /v1/integration/user/device/link

RabbitMQ Message Properties
key
value
type
USER_DEVICE_LINK
The type is expected as a property (but not in the payload) of the RabbitMQ Message. Any header will be ignored.
Kafka Message Headers
keyvalue
type
USER_DEVICE_LINK
REST API
RabbitMQ Connector
Kafka Connector

⬆️ POST /v1/integration/user/device/unlink

RabbitMQ Message Properties
key
value
type
USER_DEVICE_UNLINK
The type is expected as a property (but not in the payload) of the RabbitMQ Message. Any header will be ignored.
Kafka Message Headers
keyvalue
type
USER_DEVICE_UNLINK

Credentials

We will need you to provide us with credentials described in below link.

Best Practises for Token Management

You manage how the tokens are stored in Fast Track by using the LINK / UNLINK events (see above). Please read this article from Firebase containing Best Practise examples: