One API for every border

A single JSON API with the destination as a parameter, SIP trunks for voice, and a sandbox that returns realistic receipts before your account clears KYC.

Carry your first interaction

Sandbox keys are issued the moment you register — this exact call works against simulated destination networks while KYC is still in flight.

requestshell
curl -X POST https://api.japmtech.com/v1/interactions \
  -H "Authorization: Bearer $JAP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+55 11 90000 0000",
    "channel": "sms",
    "fallback": ["whatsapp", "voice"],
    "from": "JAP",
    "body": "Your verification code is 481902."
  }'
response202
{
  "id": "ix_7Qd2h4Kp",
  "corridor": "US→BR",
  "channel": "sms",
  "status": "accepted",
  "units": 1,
  "price": { "amount": 0.0291, "currency": "USD" },
  "trace_url": "https://console.japmtech.com/trace/ix_7Qd2h4Kp"
}

Core endpoints

POST/v1/interactionsCarry one interaction, or a batch of up to 10,000
GET/v1/interactions/{id}Fetch state and the full corridor trace for an interaction
GET/v1/numbersSearch, lease and configure inbound numbers
POST/v1/verifyStart and check a verification on the best available channel
POST/v1/webhooksRegister signed webhooks for receipts and inbound traffic

SIP and SMPP for volume

SIP trunks with TLS and SRTP for voice, and SMPP v3.4/v5 binds for high-throughput messaging, both hitting the same corridor scoring as the HTTP API. Credentials are issued by the corridor team once your account is approved.

Every interaction is traceable

A trace shows the lane chosen, the registration profile applied, each failover hop and the timestamp of the handset receipt. It is the same record our own engineers use when you open a ticket.

Move one corridor and compare

Open an account, point a single destination at JAP, and put our handset-verified delivery next to your current provider's numbers.

Median time from signup to first delivered interaction: under 20 minutes