Documentaci贸n API de Marketing SMS Gratuito
Gu铆a de integraci贸n de la aplicaci贸n m贸vil
Obtenga primero su clave API
Antes de enviar mensajes SMS de marketing gratuitos, cree una clave API personal en el panel web. Esta clave permite que su sitio web, CRM o herramienta de automatizaci贸n llame a la API directamente.
- Inicie sesi贸n en el panel web y vaya a Configuraci贸n.
- Despl谩cese hasta la secci贸n Clave API y haga clic en Generar clave.
- Copie la clave y 煤sela en el encabezado
Authorization: Bearerde sus solicitudes.
Send a Test SMS
Paste your API key, enter a phone number and message, then queue a live SMS request.
{
"status": "ready"
}
How to Send an SMS
Use queue_sms to add an outgoing SMS to the queue. The Android device/app sends it when it polls the API.
| Endpoint | POST https://api.rcszilla.com/?endpoint=queue_sms | |
| Auth | Authorization: Bearer YOUR-API-KEY | |
| to | string | Recipient phone number, with country code recommended. |
| message | string | SMS text to send. |
| channel | string | Use sms (default). Also supports whatsapp and email. For email, to is an email address, subject is required, and smtp_server_id is optional (auto round-robin when omitted). |
| subject | string | Required when channel=email. Ignored for SMS/WhatsApp. |
| smtp_server_id | int | Optional. SMTP server to send the email through; omit to auto-rotate across your configured servers. |
| scheduled_at | string | Optional date/time in YYYY-MM-DD HH:MM:SS format. |
curl -X POST "https://api.rcszilla.com/?endpoint=queue_sms" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR-API-KEY" \
-d "{\"to\":\"+40700000000\",\"message\":\"Hello from RCSZilla\",\"channel\":\"sms\"}"
{
"success": true,
"message": "Queued",
"id": 123
}
Descripci贸n general de la API
Esta es la API REST utilizada por la aplicaci贸n Android RCSZilla y el panel web para flujos de trabajo de marketing SMS gratuito. 脷sela para poner mensajes en cola, reportar el estado de entrega, enviar respuestas entrantes y sincronizar la configuraci贸n del dispositivo.
Todas las solicitudes y respuestas usan JSON. Todos los endpoints se sirven desde https://api.rcszilla.com/ y se seleccionan mediante el par谩metro ?endpoint=.
Formato de solicitud
Cada solicitud debe enviar Content-Type: application/json y un encabezado de autorizaci贸n (excepto claim_device, que es p煤blico).
POST https://api.rcszilla.com/?endpoint=queue_sms HTTP/1.1
Host: api.rcszilla.com
Content-Type: application/json
Authorization: Bearer YOUR-API-KEY
{"to": "+40700000000", "message": "Hello from RCSZilla", "channel": "sms"}
Formato de respuesta
Cada respuesta es un objeto JSON. Las respuestas exitosas siempre contienen "success": true. Los fallos contienen "success": false y un campo "message".
{
"success": true,
"message": "Queued",
"id": 123
}
{
"success": false,
"message": "id required"
}
Quick Reference
| Endpoint | M茅todo | Autenticaci贸n | Descripci贸n |
|---|---|---|---|
| queue_sms | POST | Bearer | Queue an SMS, WhatsApp, or email message to send |
| claim_device | POST | - | Register a new device (public) |
| register_device | POST | Bearer | Update device metadata |
| pending_messages | GET | Bearer | Fetch outgoing message queue |
| mark_processing | POST | Bearer | Lock a message as in-progress |
| mark_sent | POST | Bearer | Report message sent |
| mark_delivered | POST | Bearer | Report delivery receipt |
| mark_failed | POST | Bearer | Report send failure |
| submit_reply | POST | Bearer | Submit an incoming message to inbox |
| queue_status | GET | Bearer | Get single message status |
| poll | POST | Bearer | Unified heartbeat + queue + config fetch |
| heartbeat | POST | Bearer | Device keep-alive (deprecated; use poll) |
| get_config | GET | Bearer | Fetch device configuration |
| log_outgoing | POST | Bearer | Log a directly-sent message |
| ack_commands | POST | Bearer | Acknowledge processed commands |