| Name | Type | Description | Notes |
|---|---|---|---|
| type | str | <aside class="notice">Firebase Cloud Messaging has deprecated its legacy APIs for HTTP and XMPP. Legacy credentials <code>serverKey</code> and <code>senderId</code> will stop working as of June 2024 and must be replaced with OAuth 2.0 access token based credentials.</aside> To configure an android integration, first visit the Firebase Console. Generate a private key from the Service accounts tab in the settings. Copy the `project_id`, `client_email` and `private_key` from the generated JSON file and call the create integrations endpoint with this data. | [optional] [default to 'android'] |
| project_id | str | Your project ID from your generated private key file. | [optional] |
| client_email | str | Your client email from your generated private key file. | [optional] |
| private_key | str | Your private key from your generated private key file. | [optional] |
| server_key | str | Your server key from the fcm console. | [optional] |
| sender_id | str | Your sender id from the fcm console. | [optional] |
| can_user_create_more_conversations | bool | Allows users to create more than one conversation on the android integration. | [optional] |
| attachments_enabled | bool | Allows users to send attachments. By default, the setting is set to true. This setting can only be configured in Zendesk Admin Center. | [optional] [readonly] |
| default_responder_id | str | The default responder ID for the integration. This is the ID of the responder that will be used to send messages to the user. For more information, refer to <a href="https://docs.smooch.io/guide/switchboard/#per-channel-default-responder\">Per-channel default responder</a> guide. | [optional] |
| default_responder | DefaultResponderDefaultResponder | [optional] |