La Poste
La Poste is the French national postal service, offering a developer platform called Okapi that exposes REST APIs for parcel tracking, address validation, geolocation, registered letter ordering, certified document exchange (Digiposte), and open data access (dataNOVA). APIs require an X-Okapi-Key obtained by registering a free developer account.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles La Poste the way a machine reads it — 104 machine-readable artifacts across 8 APIs, 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 — La Poste scores 47.4/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile La Poste
Each block below is one kind of artifact we hold for La Poste. 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 8
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.
La Poste ControlAdresse API
Validates, standardises, and enriches postal addresses for users, customers, or prospects in France. Returns CEDEX-normalised address data including street, locality, postcode, ...
La Poste Geolocalisation API
Returns GPS coordinates for a given French postal address. Enables rapid and simple address geocoding integrated via the Okapi platform.
La Poste Geolocalisation Inversee API
Reverse-geocoding API that identifies the five closest French addresses from a given geographic point within a configurable radius.
La Poste LReL (Lettre Recommandee en Ligne) API
API for ordering online registered letters (LReL) — La Poste prints, envelopes, franks and distributes the physical letter on behalf of the requester. Uses OAuth2 authentication...
La Poste Digiposte API
Enables business applications to send certified documents directly to a recipient's Digiposte digital safe and retrieve authenticated documents with probative value from Digipos...
La Poste dataNOVA Open Data API
Open data portal powered by OpenDataSoft exposing 18+ datasets including postal office locations, street mailbox listings, postal codes (HEXASMAL), business registrations (SIREN...
La Poste SlsInternalService : Services destinés aux applications internes API
The SlsInternalService : Services destinés aux applications internes API from La Poste — 3 operation(s) for slsinternalservice : services destinés aux applications internes.
La Poste SlsServiceWS : documentation API
The SlsServiceWS : documentation API from La Poste — 9 operation(s) for slsservicews : documentation.
Scroll within the panel for all 8 ·
Pricing Plans 7
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Colissimo Plans
PLANSControladresse Plans
PLANSDatanova Plans
PLANSDigiposte Plans
PLANSLrel Plans
PLANSSuivi Plans
PLANSScroll within the panel for all 7 ·
Rate Limits 7
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Colissimo Rate Limits
RATE LIMITSControladresse Rate Limits
RATE LIMITSDatanova Rate Limits
RATE LIMITSDigiposte Rate Limits
RATE LIMITSGeolocalisation Rate Limits
RATE LIMITSLrel Rate Limits
RATE LIMITSSuivi Rate Limits
RATE LIMITSScroll within the panel for all 7 ·
FinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
La Poste Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
context Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
La Poste API Rules
SPECTRALJSON Schema 72
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ActivationDataFlavor
JSON SCHEMAAddress
JSON SCHEMAAddressee
JSON SCHEMAAddressPCH
JSON SCHEMAAddressPickupLocation
JSON SCHEMAArticle
JSON SCHEMABelgiumLabel
JSON SCHEMACategory
JSON SCHEMACheckGenerateLabelRequest
JSON SCHEMACheckInfoPlanPickupInternalRequest
JSON SCHEMACheckInfoPlanPickupResponse
JSON SCHEMACodeVAS
JSON SCHEMACommandInfo
JSON SCHEMACommandMap
JSON SCHEMAContents
JSON SCHEMACustomizationField
JSON SCHEMACustomizationFields
JSON SCHEMACustomizationTemplate
JSON SCHEMACustomsDeclarations
JSON SCHEMADataHandler
JSON SCHEMADataSource
JSON SCHEMAElementVisual
JSON SCHEMAEntityTag
JSON SCHEMAField
JSON SCHEMAFields
JSON SCHEMAGenerateBordereauByParcelsNumbersRequest
JSON SCHEMAgenerateBordereauParcelNumberList
JSON SCHEMAGenerateCN23Request
JSON SCHEMAGenerateLabelRequest
JSON SCHEMAGenerateLabelRequestV3
JSON SCHEMAGenerateLabelRequestV31
JSON SCHEMAGenerateLabelV2Response
JSON SCHEMAGetLabelInternalRequest
JSON SCHEMAGetLabelRequest
JSON SCHEMAGetListMailBoxPickingDatesResponse
JSON SCHEMAGetListMailBoxPickingDatesRetourRequest
JSON SCHEMAGetListMailBoxPickingDatesSender
JSON SCHEMAGetProductInterRequest
JSON SCHEMAGetProductInterResponse
JSON SCHEMALabelV2Response
JSON SCHEMALetter
JSON SCHEMALetterRequestV31
JSON SCHEMALink
JSON SCHEMAListMailBoxPickingDatesRetourOnlineResponse
JSON SCHEMAMediaType
JSON SCHEMAMessage
JSON SCHEMAMessageRest
JSON SCHEMAMultivaluedMapStringObject
JSON SCHEMAMultivaluedMapStringString
JSON SCHEMANewCookie
JSON SCHEMAOriginal
JSON SCHEMAOutputFormat
JSON SCHEMAParcelRequestV2
JSON SCHEMAParcelRequestV31
JSON SCHEMAPickupLocation
JSON SCHEMAPlanPickupRequest
JSON SCHEMAPlanPickupResponse
JSON SCHEMAPlanPickupSender
JSON SCHEMAReplacementValue
JSON SCHEMAResponse
JSON SCHEMAReturnAddressBelgium
JSON SCHEMARouting
JSON SCHEMASender
JSON SCHEMAService
JSON SCHEMASite
JSON SCHEMAStatusType
JSON SCHEMASwissLabel
JSON SCHEMAUriBuilder
JSON SCHEMAXmlV2Response
JSON SCHEMAZoneCABRoutage
JSON SCHEMAZoneInfosRoutage
JSON SCHEMAZoneRouting
JSON SCHEMAScroll within the panel for all 72 ·
Examples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Check Generate Label Request
EXAMPLEGenerate Label Request
EXAMPLEGenerate Label Response
EXAMPLEPlan Pickup Request
EXAMPLESecurity Posture 2
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for La Poste — 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
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
← All providers · Data indexed from github.com/api-evangelist/la-poste · machine-readable index on apis.io