D7SMS

Name: D7SMS API
Brand: D7SMS
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingbasic3 EndpointsREST

For Agents

Send single or bulk SMS messages and check D7 Networks account balance for global transactional and OTP delivery.

Quickstart

Get started with D7SMS in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a transactional SMS"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with D7SMS API.

Send a single SMS to an international destination via POST /send

Send a bulk SMS batch to many recipients in one request via POST /sendbatch

Check current D7 Networks account credit balance before triggering a campaign

Specify a custom sender ID where the destination country and operator allow

Deliver transactional one-time passwords with direct mobile network operator routing

GET STARTED

Start building with D7SMS API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for D7SMS, keeping it validated and agent-ready.

D7 Networks is a global SMS provider with direct connections to mobile network operators across the Middle East, Asia, Africa, and Europe. The D7SMS API exposes three endpoints: send a single SMS, send bulk SMS, and check account balance. It targets businesses sending one-time passwords, transactional alerts, and customer notifications who need wholesale-style direct routing rather than a marketing-focused messaging platform.

Use Cases

Patterns agents use D7SMS API for, with concrete tasks.

★ OTP Delivery for Authentication

Applications that need to send one-time passwords for login or transaction confirmation use D7's POST /send endpoint with a numeric or alphanumeric sender ID and the OTP body. D7's direct operator connections give better deliverability in emerging markets than aggregator-based providers, which matters when failed OTPs translate directly into lost sign-ups.

POST to /send with the recipient MSISDN and a body of 'Your code is 482917' and confirm the response status.

Bulk Customer Notification Campaign

Operations teams sending an outage notification or service update to thousands of customers in one go use POST /sendbatch to push the entire recipient list in a single request. The bulk endpoint is more efficient than looping over /send, and D7's wholesale routing keeps per-message cost low for large batches.

POST to /sendbatch with an array of 5,000 MSISDNs and a single message body, then read back the response to confirm acceptance.

Pre-Send Balance Check

Before triggering a high-volume SMS campaign, an operations agent calls GET /balance to confirm the account has sufficient credit. If credit is below a threshold the agent halts the send and notifies the billing owner, avoiding the failure mode where a campaign starts but only half the recipients are delivered.

Call GET /balance, parse the credit field, and return a boolean for whether the value exceeds 5,000 units.

Agent-Triggered Service Alert

An AI agent monitoring a production system detects an incident and dispatches an SMS alert to the on-call engineer through Jentic. The agent looks up the on-call number from a directory, drafts the message body, and posts to /send without needing a custom integration to D7 baked into the monitoring tool.

On detecting status='down', POST {"to":"+971501234567","content":"Service degraded"} to /send.

Key Endpoints

3 endpoints — d7 networks is a global sms provider with direct connections to mobile network operators across the middle east, asia, africa, and europe.

METHOD

PATH

DESCRIPTION

POST

/send

Send a single SMS message

POST

/sendbatch

Send a bulk SMS batch

GET

/balance

Get current account balance

POST

/send

Send a single SMS message

POST

/sendbatch

Send a bulk SMS batch

GET

/balance

Get current account balance

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

D7's HTTP Basic username and password are stored encrypted in the Jentic vault. Agents receive a scoped runtime credential when they call /send, /sendbatch, or /balance, so the raw account password is never exposed to the model context or chat logs.

Intent-based discovery

Agents search Jentic for 'send a transactional SMS' or 'send bulk SMS' and Jentic returns the matching D7SMS operation with its input schema, so the agent can call POST /send or /sendbatch directly without reading the SwaggerHub spec.

Time to first call

Direct D7SMS integration: 2-4 hours to set up auth, error handling, and balance pre-checks. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio Programmable SMS

Larger global SMS provider with richer feature surface than D7's three-endpoint REST API.

Choose Twilio when the workflow needs MMS, programmable voice, or delivery report webhooks; choose D7 when the priority is wholesale pricing for OTP and notification volume in MEA and APAC.

Alternative

Vonage SMS API

Global SMS API with similar OTP and bulk send focus and wider feature documentation.

Choose Vonage when the team already runs Vonage voice or verify; choose D7 when direct MNO routing in emerging markets is the priority.

Alternative

Plivo Messaging API

Cost-focused SMS and voice provider with similar transactional positioning to D7.

Choose Plivo when North America and Europe are the primary corridors; choose D7 for stronger Middle East and Asia routing.

Complementary

Sinch SMS API

Multi-channel messaging that can pair with D7 as a fallback route for SMS delivery.

Use Sinch as the primary route in markets where it has stronger operator coverage and fall back to D7 when delivery fails or in MEA-heavy traffic.

FAQs

Specific to using D7SMS API through Jentic.

What authentication does the D7SMS API use?

D7SMS uses HTTP Basic authentication. You supply your D7 username and password as base64-encoded credentials in the Authorization header on every request to rest-api.d7networks.com/secure. Through Jentic these credentials are stored encrypted in the vault and surfaced to the agent only as a scoped runtime credential.

Can I send a bulk SMS batch with the D7SMS API?

Yes. POST /sendbatch accepts a list of destination numbers and a single message body, so a campaign of thousands of recipients can be dispatched in one request rather than looping over /send. Use /sendbatch for any send larger than a few hundred recipients.

What are the rate limits for the D7SMS API?

The OpenAPI spec does not declare hard rate limits. D7's account-level throughput depends on the route and operator chosen at signup; for transactional traffic, treat 50 requests per second per account as a safe ceiling and use /sendbatch for higher volumes.

How do I send an OTP through Jentic?

Install pip install jentic and run an agent with the search query 'send a transactional SMS'. Jentic returns the POST /send operation with its input schema; the agent provides the destination MSISDN, the OTP body, and the sender ID, then calls execute.

Can I check my D7 SMS credit balance via the API?

Yes. GET /balance returns the current account credit. Call it before triggering a large /sendbatch to avoid the case where a campaign starts and stops mid-send because the account ran out of credit.

Does the D7SMS API support inbound SMS or delivery reports?

The three endpoints exposed in this spec are send-only and balance check. Inbound SMS routing and delivery report webhooks are configured in the D7 dashboard rather than through this REST API; you receive callbacks at a URL you supply on the account, not by calling an endpoint here.