Checks you run before taking a piece of data at face value: signing someone up, sending them a verification code or accepting a payment.

Every check goes through the same call. The SERVICIO parameter picks which one, and parameters that do not belong to that check are ignored: you can always send the same structure and only change SERVICIO. New checks (email, IP…) will arrive here, with no second URL for you to integrate.

Of everything you can learn about a number without calling it, these two are the ones that actually change a decision.

The porting date. A number that changed carrier three days ago, right before a significant operation, is the signature of a SIM swap: the attacker moves the victim's number to another carrier and from then on receives their verification codes. If you are about to send a code to that number, verify through another channel first.

The line type. An Internet line (VoIP) where a mobile should be is usually a throwaway number: minutes to get, minutes to abandon. And premium-rate or machine-to-machine numbering is nobody's personal phone.

On top of that, the response carries a calculated risk from 0 to 100 with the reasons in plain text. It is not a verdict and it does not decide for you: it is what the data supports, explained, so your system can apply your own policy.

For Spanish mobile numbers we use our own porting registry, which is what lets us tell you the carrier the number came from and the exact date of the change. For Spanish landlines and any foreign number we query international numbering data. You do not have to choose: send the number and it is resolved wherever it has to be.

The Fuente field of the response tells you which was used. Not every country publishes porting history: when there is no data, Portabilidad.Consta comes back as 0 —which is not the same as «not ported», and that is why they are told apart.

You are charged per resolved check. If it cannot be resolved the call returns -4 and nothing is charged.

The same check repeated within a minute (a double submit, a retry from your system) returns the previous result flagged with Repetida=1 and is not charged either. After that minute it is looked up again for real and charged again: the data may have changed, and yesterday's porting is precisely the one you care about.

Same as the rest of our APIs: Basic authentication with your user and your API Token, which you will find in your panel under Your data → Configure → Security. Remember to authorise there the public IP address you will be calling from.