Plumma CONNECT API
A single-operation aggregation API over mobile network operator intelligence. One POST /api call carries a phone number in E.164 form plus a `commands` array, and returns the requested signals in one response. The published enum carries 17 commands — line_classification, current_carrier, issuing_carrier, porting_timestamp, porting_logs, network_presence, roaming_intel, deactivation_point, churn_tracker, sim_swap, port_fraud_shield, digital_footprint, age_verification, kyc_match, divert_detector, commercial_segment and tenure_period. Authentication is a single API key header (x-plumma-connect-api-key, documented as a base64-encoded X.509 client certificate). Errors are RFC 7807 problem documents on every 4xx/5xx, carrying a correlation_id. The specification ships four worked request examples, including a multi-command call.
Plumma CONNECT API is published by Plumma on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 1 JSON Schema definition.
Tagged areas include Network APIs, SIM Swap, KYC, Age Verification, and Fraud Prevention. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and 1 JSON Schema.
This API exposes 1 operation across 1 path, and defines 21 schemas. It is described by OpenAPI 3.1.0, at version 1.0.2-20260903172027.
Requests are made against a single base URL, https://connect.plumma.it/services.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Plumma CONNECT API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as x-plumma-connect-api-key (ApiKeyAuth).
ApiKeyAuth— Your X.509 client certificate, base64-encoded.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
The flagship aggregation endpoint.
Schemas 21
The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are PlmResponse (27 properties), DigitalFootprint (15 properties), KycResults (14 properties), Address (9 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
This is an independent, third-party profile of Plumma CONNECT API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.