Introduction

Plumma® Connect gives you mobile network intelligence through one API. You do not build and maintain a separate integration with each mobile network operator. You send one call, and Plumma® Connect routes it to the right source for the number.

What Plumma® Connect solves

Mobile networks know things about a phone number, and the device behind it, that no other data source can provide. Getting that data used to mean negotiating with each operator separately, coping with APIs that differ from one operator to the next, and fixing integrations every time an operator changed its systems.

Plumma® Connect takes that work off your hands. Network operators and their authorized partners sit behind a single endpoint. For every request, Plumma® Connect picks the best available source for the number's country, so a SIM swap check, a carrier lookup or a subscriber identity match is always the same call, whichever network the number belongs to.

Commands

Each capability is a command: a named check, such as sim_swap, kyc_match, current_carrier or porting_timestamp, that is answered in real time.

A single request carries one phone number in E.164 format and the list of commands you want answered for it. The answer arrives synchronously as one JSON response. Only the blocks of the commands that were served are filled in, and the rest are left out. This keeps the API easy to fit into authentication, onboarding and fraud prevention flows.

For example, sim_swap reports how recently the SIM card behind a number was changed, from "no swap observed" to "within the last 24 hours". A recent swap is a strong sign of account takeover fraud.

An HTTP 200 means the request was processed. It does not mean every command was served: read the status and status_message fields of the response to see which were.

Getting access

Every call is identified by two headers: your client certificate and the application the call belongs to. Plumma enables each certificate for a specific application, so a new key or a new application works only after Plumma has enabled it. The Authentication section has the details.

Demo numbers

For development and testing, Plumma provides a set of demo numbers. They go to the same endpoint as live traffic and return synthetic but consistent data: the same number always gets the same answer, and every command you request is served. Each demo response identifies itself in its status_message.

Demo responses have the same structure and value ranges as live ones, and they use the same endpoint. An integration built against demo numbers therefore works on real numbers without any change.

Billing

You pay for each command that was actually served, never for each API call. A command is not charged when its country is not covered, when the source failed to answer, or when the request was rejected during validation. A "no data held for this number" answer still counts as served, and is charged.

OpenAPI descriptor

The full Plumma® Connect API is described in an OpenAPI 3.1 specification. Download the descriptor and import it into Postman or any compatible tool to explore the endpoint, its parameters and its response schemas. A standalone JSON Schema, plmrequest.schema.json, lets you validate a request before you send it.