Carnival Mobile
Carnival Mobile (carnival.io) was a mobile relationship management platform, backed by GV, that let marketers segment users and deliver push notifications, in-app messages, rich media and an in-app message stream from inside native iOS and Android apps. Sailthru acquired Carnival and rebranded the product Sailthru Mobile; it ships today as the Marigold Mobile SDK. The lineage is still directly observable: docs.carnival.io 301-redirects to docs.mobile.sailthru.com, which 301-redirects to sdkdevelopers.meetmarigold.com, and the current documentation still carries Carnival-era pages such as the iBeacons guide. The original carnivalmobile GitHub organization remains public, and the iOS, Android and React Native SDKs are still published to CocoaPods and npm under the first-party "carnival" maintainer account, which makes them the continuing distribution path for this company's developer surface. Carnival Mobile has no independently documented public REST API; its developer contract is an on-device SDK.
Carnival Mobile is profiled on the APIs.io network. Tagged areas include Company, Enterprise, Mobile, Push Notifications, and In-App Messaging.
Carnival Mobile’s developer surface includes developer portal, documentation, getting-started guide, support, changelog, sandbox, and 16 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Mobile SDK Publishers (Play SDK Index, CocoaPods, ADA certification) | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.