Utility to add auth headers to content requests for restricted Help Centers

A user in Zendesk.

User Field in Zendesk

Dropdown userfields can contain User fields options which describe an option in the dropdown

An objective-c visible class for the Push Registration Provider Provider to register and unregister a device for push notifications.

An objective-c visible class for the User Provider

An object which describes an ActionHandler.

A registry of objects to be used for inter-SDK actions, such as starting a view controller from one SDK, in another SDK, without any dependency between them.

The Zendesk Application information

Storage for values that live for a device install.

Public model used to allow consumers to send PageView Blip data

Public model used to allow consumers to send UserAction Blip data

Store the application session to user deaults

Provides an API to interact with a zendesk user object

Defines a handler for an inter-SDK action, such as one SDK starting another one, without either SDK having a dependency on the other. An example of this would be a hypothetical Help Center SDK starting the "create ticket" screen of the Support SDK. In order to properly separate SDKs from each other, handlers will work on "action Strings". Multiple SDKs can be capable of handling the same action String. For example, a "contact us" action can be handled by Support, Chat, Voice, Message, etc. In the event that more than one ActionHandler has been registered for the same actionString, the priority variable can be used to determine which one to call the handle method on.

Type alias for a network completion handler.