Application Object

Object Information

ID and Tag

You can identify an application by either an ID number (e.g. 120) or by tag (e.g. netify.twitter). The "netify" prefix on the application tag is the default, so it can be omitted. For example, both netify.twitter and twitter tags identify the Twitter app. You can browse the list of tags on the applications lookup web tool or you can fetch the list by querying the REST API.

Label / Full Label

The label is the name an end user would typically use to identify an application, while the full_label (if shown) provides a more formal name. For example, "BBC" is the label, but "British Broadcasting Corporation" is the full_label.


The description is a one or two sentence description of the application.

Home Page

The home_page provides the link to the application home page.


Every application is listed under a primary category. You can find a list of application categories and associated IDs / tags here.


Applications can come and go - merger & acquisitions, bankruptcy, etc. The active flag is set to false for any applications that have been retired.

Application Object JSON Example

"application": {
    "id": 120,
    "tag": "netify.twitter",
    "label": "Twitter",
    "full_label": "Twitter",
    "description": "Twitter is a ...",
    "home_page": {
        "url": "",
        "text": "Twitter"
    "category": {
        "id": 24,
        "tag": "social-media",
        "label": "Social Media"
    "active": true,
    "favicon": "",
    "icon": "",
    "logo": "",
    "favicon_source": "app",
    "icon_source": "app",
    "logo_source": "app"


Three types of logos are available in the data payload. The favicon and icon can be any size, but these images will render well at the sizes described in the adjacent table. The logo, on the other hand, is strictly 128x128.

Key Description
favicon A logo that renders well at 16x16
icon A logo that renders well at 128x128
logo A logo that is exactly 128x128

Not all applications have all of the logos available. By default, the REST API response will provide a placeholder logo showing the first letter of the app, e.g. .

In the data payload, you can check the values for favicon_source, icon_source, and logo_source to verify the source of the images. If the source is set to app, the real application logo is available. If the source is set to default, the placeholder image is provided.

Other Data Objects

Integration and Custom Solutions

Do you have any questions about integration, APIs or custom development?

Contact Us