SIM7 DEVELOPERS
Connect Sim7 to your product
Reference clients and a workflow for the live API. Keys stay server-side and purchases require explicit confirmation.
Start with a runnable example
Python, Node.js and n8n: stable purchase IDs, multiple SMS and safe event handling. The examples never finish a number after the first code.
From a first request to repeat purchases
Choose your stack and download the source. Python uses only the standard library, Node.js uses built-in fetch and SQLite, and n8n uses standard HTTP Request, Code and Wait nodes. These are server-side examples, not a way to embed a secret key into a public page.
Start with balance and catalog reads. Copy service, country and operator IDs from the API; prices are in USD. A live purchase spends real balance and max_price caps the chosen offer. Prices are specific to your key, so do not build accounting around another person's screenshot.
Each customer operation needs one stable business_id. A network failure must never automatically generate a new key and replacement purchase. Python and Node.js persist the request before sending and the receipt afterwards; n8n requires persistent order fields from your own system. Reconcile uncertain outcomes before creating a new sale.
Messages and order completion
An order response contains messages[], not only the latest code. code_received is not completion: applications can keep observing and show subsequent messages to the owner. Request another code in the target service; Sim7 has no universal API to make another platform send an SMS.
Webhooks accelerate updates but require raw-body signature verification and durable storage before acknowledgement. Deliveries may repeat or arrive out of order. Python and Node.js include a signed durable inbox; fulfillment remains your business transaction. Never treat an unsigned public callback as authority for financial credits.
See the API reference for fields, scopes, errors and current limits. Example checks use controlled test responses without supplier purchases. Before commercial launch validate customer authorization, financial reservation, refunds and log hygiene so keys and SMS cannot leak.

