NestJS SMS Gateway with Android Device: Queue Workers

Featured illustration for NestJS SMS Gateway with Android Device: Queue Workers

Bull/BullMQ processors in NestJS for Android SMS gateway API sends: dual-SIM adjacency, Shopify contrast.

Written by the SMS Gateway team for operators who run phones and airtime themselves — not for theoretical cloud SMS demos.

InformationAndroid SMS GatewayAPIDevelopers
Article
Published
November 25, 2024
Updated
January 1, 2025
Reading time
16 minute read

Key Takeaways

  • NestJS queue workers send OTP and alerts by HTTPS/JSON from a processor — not a Nest SMS SDK product.
  • Bull/BullMQ retries without an idempotency key duplicate codes and burn operator airtime.
  • HTTP 201 is accepted. Persist gateway ids. DLR/webhooks close delivery. Confirm fields in Developer Center.
  • Pace workers to one OTP device. Starter’s extra slot is a spare chassis, not two radios in one phone.
  • You bring the Android and operator credit. Platform pricing is devices plus send volume.

android sms gateway api from NestJS workers is a processor plus a paired phone. OTP sibling: NestJS OTP. Notifications: notifications. Retries: retry policies. Live JSON: Developer Center.

You bring the handset and airtime. Devices and send volume. REST samples are HTTPS/JSON — not NuGet, Composer, or a Nest SDK.

BullMQ · processor · SIM

Five workers do not make five modems.

BullMQ is not a second radio

Conceptual processor only — confirm path and JSON in Developer Center:

@Processor('sms-send')
export class SmsSendConsumer {
  async process(job: Job<{ clientRef: string }>) {
    // POST HTTPS with env token; persist gateway id
  }
}

Keys: env. Pair: Downloads. Queue backlog: backlog.

defaultJobOptions.attempts: 8 with a new OTP each attempt is how Nest “reliability” becomes eight texts and a locked-out user.

Worker table

QueueConcurrencyOn failDevice
otp-sendLowDo not mint a new codeQuiet OTP SIM
order-alertModestIdempotent client_refTransactional SIM
promoPaced to radioStop on 429 / throttleNever the OTP SIM
dlr-ingestFast persistSticky Delivered

Concurrency vs the SIM

Starter allows 2 devices — spare chassis. Throughput per SIM. Dual SIM is not two workers. Transactional SMS.

OTP jobs vs campaign jobs

Order alerts: order alerts. Shopify is a different last mile — contrast only. DLR, webhooks. NestJS queues. Messaging practices.

Next steps

One otp-send job, client_ref required, canary to staff. Spend 300 lifetime SMS proving the processor — then a funded SIM.

Jump to the live product docs for this topic—not another long-form article.

FAQ

Frequently asked questions

Direct answers about android sms gateway api.

How do NestJS queue workers talk to an Android SMS gateway?

Enqueue a DTO with to, text, client_ref, device_id. The processor POSTs REST using env credentials. Persist the message id. Map DLR later. Copy live JSON from Developer Center.

Is there a NestJS SDK?

No Complete SDK. Use HttpModule / fetch. HTTPS/JSON only.

Does a worker include carrier SMS credit?

No. Free is 300 SMS lifetime for proofs.

Should OTP and Shopify-style order alerts share a queue?

Share Redis if you want. Separate job names, concurrency, and device_id.

Where are live API fields?

Developer Center.
Keep learning

Topically related guides—chosen by subject overlap, not a fixed sitewide footer.

Information
android sms gateway api multi device

Android Sms Gateway Api Multi Device: In-Depth Guide

Android Sms Gateway Api Multi Device: In-Depth Guide. Long-tail article focused on exact query "android sms gateway api multi device". Expand with examples, limits, FAQ, and links to hub C. Priced by devices and SMS send volume; BYO phone and operator credit. Developer Center owns live API parameters.

Jun 21, 202616 min
Read article
Information
android sms gateway multi device

Android SMS Gateway multi-device failover: Api usage

Android SMS Gateway multi device failover — device failover-api usage. Feature deep dive on multi-device failover (api usage). Unique examples and failure modes; link matching /features path when exists. Priced by devices and SMS send volume; BYO phone and operator credit.

Jun 2, 202516 min
Read article
Information
android sms gateway otp queue

Android SMS Gateway OTP priority queue: Api usage

Android SMS Gateway otp priority queue — api usage. Feature deep dive on OTP priority queue (api usage). Unique examples and failure modes; link matching /features path when exists. Priced by devices and SMS send volume; BYO phone and operator credit.

Aug 27, 202616 min
Read article

Browse the full Android SMS gateway knowledge base or return to how an Android SMS gateway works.

Get started

Test the gateway on your own Android phone

Install the app, pair one device, and validate your API flow before choosing a paid plan.

You supply the phone, SIM, and operator SMS credit.