> ## Documentation Index > Fetch the complete documentation index at: https://novu-c5de82d9-docs-homepage-redesign.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Subscriber schema > Reference the Novu subscriber schema used in API requests and responses. Review fields, data types, and object structure for this resource. ### Subscriber Subscriber is the end user that receives notifications. Subscriber has subscriber attributes like firstName, lastName, email, phone, etc, `data` field to store any custom attributes in key value pairs and channel credentials for push and chat channel provider's integrations. Read more about subscribers on [subscribers concept page](/platform/concepts/subscribers). The internal ID generated by Novu for your subscriber. This ID does not match the `subscriberId` used in your queries. Refer to `subscriberId` for that identifier. The first name of the subscriber. The last name of the subscriber. The email address of the subscriber. The phone number of the subscriber. The URL of the subscriber's avatar image. The locale setting of the subscriber, indicating their preferred language or region. An array of channel settings associated with the subscriber. An array of topics that the subscriber is subscribed to. Indicates whether the subscriber is currently online. The timestamp indicating when the subscriber was last online, in ISO 8601 format. The version of the subscriber document. Additional custom data for the subscriber Timezone of the subscriber The identifier used to create this subscriber, which typically corresponds to the user ID in your system. The unique identifier of the organization to which the subscriber belongs. The unique identifier of the environment associated with this subscriber. Indicates whether the subscriber has been deleted. The timestamp indicating when the subscriber was created, in ISO 8601 format. The timestamp indicating when the subscriber was last updated, in ISO 8601 format. ### ChannelSettingsDto ChannelSettings are credentials for push and chat channel provider's integrations. One subscriber can have credentials for multiple integrations of same provider of one channel type The provider identifier for the credentials The integration identifier Credentials payload for the specified provider The unique identifier of the integration associated with this channel. ### Credentials Credentials like deviceTokens, webhookUrl, etc for a specific integration. `providerId` could be chat channel providerId or push channel providerId.