Isendpro API iSendPro

Name: API iSendPro API
Brand: API iSendPro
Availability: InStock

✓ Official Vendor SpecCommunicationsSms MessagingapiKey14 EndpointsREST

For Agents

Send single or bulk SMS messages, validate numbers via HLR, manage directories and blocklists, and pull campaign recaps from the iSendPro French SMS gateway.

Install Jentic One Beta

Connect the API iSendPro to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API iSendPro, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with API iSendPro API.

Send a single SMS to a French or international mobile number with optional sender ID

Broadcast SMS to a list of recipients in one call via the smsmulti endpoint

Validate a mobile number with an HLR lookup before charging the campaign

GET STARTED

Start building with API iSendPro API

Explore with Jentic

View OpenAPI Document

iSendPro is a French SMS gateway run by CALL ON IT covering single and bulk SMS delivery, HLR lookup, contact directory management, blocklist administration, and subaccount provisioning. The 14 endpoints support sending one-shot SMS via POST /sms, broadcasting through POST /smsmulti, retrieving campaign recaps, validating numbers via HLR, generating short links, and metering character counts before send. Authentication is a per-account keyid passed in the request body alongside an IP allow-list configured in the iSendPro dashboard.

Use Cases

Patterns agents use API iSendPro API for, with concrete tasks.

★ Transactional SMS delivery for French ecommerce

Send order confirmations, delivery alerts, and OTP codes to French and European customers through POST /sms. iSendPro routes via tier-1 carriers and supports custom alphanumeric sender IDs where local regulation allows. Integration takes a couple of hours including HLR validation and credit-check wiring.

Send the message 'Votre commande #4231 est expediee' to phone number 33612345678 with sender ID 'BOUTIQUE'

Bulk marketing campaign with opt-out enforcement

Run a marketing SMS broadcast against a contact directory while honouring blocklisted numbers. The agent posts the recipient list to POST /smsmulti, then queries POST /campagne for the per-message status. Numbers added to the blocklist via POST /setlistenoire are filtered out automatically by iSendPro before billing applies.

Broadcast the message 'Soldes -30%' to the directory 'newsletter-fr' and skip numbers on the blocklist

Number validation pipeline before campaign send

Reduce wasted SMS credit by running an HLR lookup against every recipient via POST /hlr before broadcasting. Invalid or unreachable numbers are removed from the campaign so the spend lands only on numbers with active SIMs. Combined with the POST /comptage character-count check, the agent can predict campaign cost to within a few percent.

For each number in the supplied CSV, run POST /hlr and write back active or inactive status

AI agent customer support SMS notifications

An AI customer support agent can fire SMS alerts during workflow handoffs without operating a separate SMS integration. Through Jentic the agent searches for 'send a French SMS' and the matching iSendPro operation is loaded with the keyid already injected from the vault. Lets the agent close the loop with the customer over the channel they actually read.

After a refund is approved, send the customer at 33612345678 the message 'Remboursement approuve, sous 3 jours ouvres'

Key Endpoints

14 endpoints — isendpro is a french sms gateway run by call on it covering single and bulk sms delivery, hlr lookup, contact directory management, blocklist administration, and subaccount provisioning.

METHOD

PATH

DESCRIPTION

POST

/sms

Send a single SMS

POST

/smsmulti

Broadcast SMS to multiple recipients

POST

/hlr

Validate a number via HLR lookup

POST

/campagne

Retrieve campaign recaps

POST

/credit

Get remaining account credit

POST

/comptage

Count characters of an SMS body

POST

/setlistenoire

Add a number to the blocklist

POST

/shortlink

Generate a trackable short link

POST

/sms

Send a single SMS

POST

/smsmulti

Broadcast SMS to multiple recipients

POST

/hlr

Validate a number via HLR lookup

POST

/campagne

Retrieve campaign recaps

POST

/credit

Get remaining account credit

POST

Why Jentic?

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

Credential isolation

iSendPro keyid values are stored encrypted in the Jentic vault. Agents receive scoped execution tokens — the raw keyid never enters the agent context, which matters because iSendPro charges per SMS sent.

Intent-based discovery

Agents search by intent (e.g. 'send a French SMS' or 'validate phone number HLR') and Jentic returns the matching iSendPro operation with its body schema — including the often-overlooked sms array structure.

Time to first call

Direct iSendPro integration: 4-8 hours to wire the JSON-in-body keyid pattern, IP allow-list, HLR pre-flight, and campaign recap polling. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using API iSendPro API through Jentic.

What authentication does the iSendPro API use?

iSendPro authenticates with a per-account keyid sent inside the JSON request body, alongside an IP allow-list configured in the iSendPro dashboard. The keyid is generated under the 'mon compte' panel of the iSendPro account. Through Jentic the keyid is held in the vault and injected at request time.

Can I send bulk SMS in a single call?

Yes. POST /smsmulti accepts a list of recipients in one request and returns a per-message status array. For very large lists the request can be split into batches; recap retrieval through POST /campagne reconciles the status of each message later.

What are the rate limits for the iSendPro API?

Hard rate limits are not declared in the spec. iSendPro applies a fair-use ceiling tied to the account's monthly volume tier, with the IP allow-list serving as the practical gating mechanism. Confirm the account-level throughput before driving very large bursts.

How do I validate a mobile number before sending through Jentic?

Search Jentic with the query 'validate French mobile number' or 'HLR lookup', load the POST /hlr operation, and execute it with the recipient phone number. The response indicates whether the number is active and which operator is hosting it.

Is the iSendPro API free?

iSendPro is a paid service. New accounts can request a test credit on application; production usage is billed per SMS with volume tiering. Check current pricing on the iSendPro website before forecasting campaign cost.

Does iSendPro support short links inside SMS?

Yes. POST /shortlink generates a trackable short URL that can be embedded in the SMS body. Click counts are then surfaced through the campaign recap endpoint.

Isendpro API iSendPro

Connect the API iSendPro to your agent

Capabilities

Start building with API iSendPro API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs