Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Rappi website screenshot

Rappi

Rappi is a Colombian-founded pan-Latin American super-app headquartered in Bogotá, with regional hubs in São Paulo and Mexico City. Founded in 2015 by Simón Borrero, Sebastián Mejía, and Felipe Villamarín, and accelerated through Y Combinator's W16 batch, Rappi operates across Argentina, Brazil, Chile, Colombia, Costa Rica, Ecuador, Mexico, Peru, and Uruguay. The platform bundles on-demand delivery (restaurants, groceries via "Súper" and Turbo Fresh, pharmacies, retail, alcohol) with consumer fintech (RappiPay, RappiCard, RappiCash) and adjacent services such as RappiTravel and the RappiPrime subscription. Rappi's developer surface is operated through its Partners program at dev-portal.rappi.com, where approved restaurants, retailers, and middleware providers obtain OAuth 2.0 client credentials to integrate with a REST API for menu and catalog management, store availability, order lifecycle events, financial reconciliation, and webhook subscriptions. Access is not self-serve — a Rappi business contact must approve onboarding, after which partners receive development-environment credentials and an integration path to production. SoftBank-backed since 2019, Rappi competes regionally with iFood, Uber Eats, and DiDi Food, with fintech ambitions overlapping Nubank, Mercado Pago, and regional neobanks.

agent aware

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Rappi the way a machine reads it — 21 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Rappi scores 17.9/100 (emerging), with a separate agent-readiness read of 15/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 17.9/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 5.7 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 2.7 / 13
Governance 0.0 / 12
Discoverability 8.0 / 10
Regulatory · Payments 3.9 / 15
Agent readiness — 15/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Rappi

Each block below is one kind of artifact we hold for Rappi. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 1

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Rappi Partners REST API

The Rappi Partners REST API is the integration surface used by approved restaurants, grocery and retail merchants, and middleware/POS providers to operate on the Rappi marketpla...

Features 6

The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.

Notable capabilities this provider offers.

On-Demand Delivery

Restaurant, grocery (Súper), pharmacy, retail, and alcohol delivery fulfilled by the Rappi courier fleet across nine LatAm countries.

Turbo Fresh

Sub-15-minute grocery and convenience delivery from Rappi-operated dark stores in major metropolitan areas.

RappiPay & RappiCard

Consumer fintech wallet, debit, and co-branded credit card products embedded in the super-app and operated as regulated entities in select markets.

RappiTravel

In-app flights, hotels, and travel booking surface integrated with the Rappi wallet and loyalty stack.

RappiPrime Subscription

Recurring membership offering free delivery, exclusive discounts, and partner perks across the super-app verticals.

Partners Developer Portal

OAuth-secured REST API for menus, availability, orders, stores, financial reconciliation, and webhooks, gated behind manual partner onboarding.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Rappi Domain Security

TLSv1.3 · DMARC

SECURITY

Use Cases 5

What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.

What developers build with this provider.

POS & Aggregator Integration

Restaurant POS vendors and order aggregators sync menus and push/pull orders between merchant systems and Rappi storefronts.

Grocery & Retail Catalog Sync

Supermarket and convenience chains keep large SKU catalogs and real-time stock availability synchronized with Rappi store pages.

Order Lifecycle Automation

Brands receive Rappi orders via webhook, route them to kitchen or fulfillment systems, and progress status back through the API.

Financial Reconciliation

Merchants pull payout, commission, and settlement data through the Financial endpoints for accounting and FP&A pipelines.

Last-Mile as a Service

Enterprise brands tap the Rappi courier fleet for branded last-mile delivery in LatAm metros.

Integrations 4

Pre-built integrations with other platforms tell you where this provider already fits in a stack.

Pre-built integrations with other platforms and tools.

Restaurant POS Systems

Middleware providers connect kitchen and POS platforms to the Rappi Rests API for menu and order flow.

Grocery & Retail ERPs

Catalog, pricing, and inventory systems push availability updates through the Partners API.

Payment Networks

RappiPay and RappiCard integrate with regional card networks and local payment rails per country.

Travel Suppliers

RappiTravel aggregates flight and hotel inventory from third-party GDS and travel partners.

Solutions 4

Packaged solutions the provider offers on top of the raw API surface.

Packaged solutions this provider offers.

Restaurants

Onboarding, menu management, order capture, and reconciliation tools for restaurant brands on the Rappi marketplace.

Grocery & Retail

Catalog, stock, and store-availability tooling for supermarket, convenience, and specialty retail partners.

Brands & Enterprises

Last-mile fulfillment and Rappi-native commerce for enterprise brands seeking LatAm coverage.

Consumers

The Rappi super-app for delivery, fintech, travel, and Prime subscription benefits across nine countries.

Resources

Every other property we hold for Rappi — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Other 4

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/rappi · machine-readable index on apis.io