listing

The listing block is required. It is everything a connector says about itself to people who have not installed it: the marketplace card, the connector's public page, the in-app directory, GET /connectors and the MCP catalogue all read it, and nothing on those surfaces is typed by hand. What a connector cannot say about itself (whether it is official, available, new or trending) the registry stamps.

"listing": {
    "category": "messaging",
    "tagline": "Sell access to Telegram channels, groups and supergroups through your own bot.",
    "overview": "Connect a bot you created with @BotFather and Subscriby runs your membership on Telegram: …",
    "screenshots": [],
    "links": {
        "documentation": "https://docs.subscriby.net/guide/connectors/telegram",
        "support": "mailto:[email protected]",
        "privacy": "https://telegram.org/privacy",
        "terms": "https://telegram.org/tos",
        "homepage": "https://telegram.org"
    },
    "added_at": "2025-04-21",
    "changelog_url": "https://www.subscriby.net/blog",
    "sign_in_required": false,
    "portal_cta": { "label": "Open Telegram Bot" },
    "marketing": {
        "audience": "Telegram communities",
        "place": "channel",
        "places": "channels, groups and supergroups",
        "installation": "bot",
        "identity": "Telegram account",
        "native_payment": "Telegram Stars"
    }
}

The fields

The links

• documentation: your own guide for creators using the connector (how to install it, what members experience), not this SDK reference.
• support: where a creator writes when the connector misbehaves; a mailto: is fine.
• privacy and terms: the platform's policies, not yours. The marketing site's legal pages link the available connectors' privacy for members' reference, so it must be the document a member's data on that platform is governed by.
• homepage: the platform's site.

marketing

The public site never spells a platform. Its copy carries tokens that are filled from the connectors available on that installation of Subscriby, so a sentence written once names Telegram today and whichever connector is available tomorrow. Your marketing block supplies the words:

The first five are required inside the block; native_payment is optional. The connector's name fills :platform, and every available connector together fills :platforms; the connectors being built fill :next and the roadmap fills :planned on the home page. A sentence built on a word your block does not supply is dropped rather than rendered half-empty: a comparison row about native payments disappears when no available connector declares one. Write the words in lower case except the platform's own proper nouns, and as they would read mid-sentence ("your :place", "a :platform :installation"). A connector that lends no words leaves the block out; every connector still gets its own marketplace page from the rest of the listing.

portal_cta

"portal_cta": { "label": "Open Telegram Bot", "icon": "paper-airplane" }

The member portal's header shows one button per installed connector that has somewhere to open: label (a translation key) and an optional icon, a key from Subscriby's connector icon set; when it is omitted the connector's own icon is drawn, which is almost always right. The core addresses the button through InstallationLifecycle::startLink(), so the connector never builds the URL here. Omit the block when the platform has nothing a member opens (a role gate shows itself). The same block is returned in GET /connectors so the creator apps render it identically.

What the registry stamps

These are never in the manifest, so a package cannot claim them: