Skip to content
Intracent
Log in Talk to sales Start building
Verify (OTP & 2FA) Products Virtual numbers Wholesale SMS Industries Developers API reference Pricing Compliance Log in
Talk to sales Start building
Examples
Documentation 1-way & 2-way SMS

Intracent API documentation

Connect your application to Intracent to send and receive SMS worldwide and look up numbers in real time. Choose the interface that suits your stack. REST, HTTP and SMPP all support 1-way and 2-way messaging on the same carrier routes.

Choose your API

Customer portals

Your EDRs (event data records), invoices and traffic statistics live in the portal linked to your interface.

REST API customers
sms.intracent.com ↗

Web platform, API Connections, tokens, EDRs, invoices and stats.

HTTP API & SMPP customers
portal.intracent.com ↗

EDRs, invoices and statistics for HTTP and SMPP interconnections.

Quickstart: your first SMS over REST

  1. 1
    Log in to the platform
    Sign in at sms.intracent.com. Your REST credentials and stats live here.
  2. 2
    Create an API connection
    Go to Platform → API Connections → + Add, then copy the username and password it generates.
  3. 3
    Get a Bearer token
    Call GET /rest/auth with Basic credentials, or use API Connections → Get Token in the platform.
  4. 4
    Send your first SMS
    POST /rest/send_sms with your token, acc_id, from, to and message.
  5. 5
    Track delivery
    Give us an HTTPS URL for delivery receipts, or check status in the platform.
REST API
JSON over HTTPS with token authentication
https://api1.intracent.com/rest

Authentication

The REST API supports two authorization types. Both use the credentials of a user created on your Intracent platform account.

Basic

Login and password are base64-encoded and sent in the Authorization header of each request. It's stateless and works for almost every method except POST send_sms.

Bearer token recommended

Call GET /auth with Basic credentials to receive a token, then send Authorization: Bearer <token>. Bearer is required for sending SMS.

lifetime
decimal · days optional
Token lifetime. Default is 2 hours. Min 0.000694 (1 minute), max 365 (1 year).
IP-bound tokens. A token works only from the IP address that requested it. Using it from another address, or after it expires, returns HTTP 426. Two-factor login on? Basic requests fail with ERR-2FA-AUTH-ERR, so get a token instead, with Basic credentials of login:password:code (code = your current authenticator code).
GET /rest/auth · cURL
# lifetime is in days (default 2 hours, min 0.000694, max 365)
curl -u 'LOGIN:PASSWORD' \
  'https://api1.intracent.com/rest/auth?lifetime=1'
Using the token
curl -H 'Authorization: Bearer <TOKEN>' \
  'https://api1.intracent.com/rest/<method>'

Methods & conventions

Resources are managed with standard HTTP verbs. Not every resource supports every verb.

GET
Retrieve records, e.g. GET balance (your account balance), GET user or GET user/{id}.
POST
Add new records, e.g. POST user, POST send_sms.
PUT
Modify an existing record, e.g. PUT user/{id}, PUT user_password.
DELETE
Delete a record, e.g. DELETE user/{id}.

Dates use YYYY.MM.DD HH24:MI:SS, e.g. "start_date": "2018.01.01 01:00:33". A date without a time is read as 00:00:00.

POST / GET /send_sms Bearer only

Send an SMS

Send one message to one or more recipients (up to 100), with POST or GET. If the message can't be routed, the API returns HTTP 400. If your account has no rate for the destination, the body says Rate not found for accountId….

acc_id
integer required
Your account ID. You can send username + password instead.
username / password
string optional
Credentials from the API Connections tab in the Intracent platform. Use these instead of acc_id.
from
string required
Sender ID (alphanumeric or number).
to
string required
Destination number(s). Up to 100, comma-separated.
message
string required
Message text.
campaign_id
integer optional
Assigns the message to a campaign.
message_label
string optional
Your own label, saved with the message records (EDRs).
POST /rest/send_sms · cURL
curl -X POST \
  -H 'Authorization: Bearer <TOKEN>' \
  -H 'Accept: application/json' \
  'https://api1.intracent.com/rest/send_sms?acc_id=<ACC_ID>&from=Intracent&to=61412345678&message=Hello%20from%20Intracent'
200 OK · message_text is base64
{
  "message_id": "test34-20190719160918482277-7a01fa",
  "message_text": "dGVzdA=="
}
POST /bulk_send_sms

Send in bulk

Send many messages in one request. Each one can have its own sender and text. The request body is a JSON array of message objects, sent one by one. Keep each call under 20,000 messages and run no more than 3 or 4 calls at once: the default speed is 20 to 30 messages a second and the connection closes after 15 minutes. campaign_id has no effect here, so tag bulk sends with message_label.

acc_id
integer required
Your account ID. You can send username + password instead.
body
JSON array required
Array of objects, each with from, to (comma-separated for several numbers) and message.
show_details
0 | 1 optional
Set to 1 to return message_id, dnis, segment_num and http_status for every attempt.
message_label
string optional
Your own label for this batch, saved with the message records.
Response fields
sentCount
integer
Messages sent.
rejectedCount
integer
Messages rejected.
totalCount
integer
Total attempts.
details
array
Per-recipient results. Only returned when show_details=1.
POST /rest/bulk_send_sms · cURL
curl -X POST \
  -H 'Authorization: Bearer <TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '[
    {"from":"Intracent","to":"61412345678","message":"Hello world 1"},
    {"from":"Intracent","to":"61412345679,61412345680","message":"Hello world 2"}
  ]' \
  'https://api1.intracent.com/rest/bulk_send_sms?acc_id=<ACC_ID>&show_details=1'
200 OK · show_details=1
{
  "sentCount": 2,
  "rejectedCount": 1,
  "totalCount": 3,
  "details": [
    { "message_id": "test34-20190719165631320270-d47075",
      "dnis": "61412345678", "segment_num": 1, "http_status": 200 },
    { "message_id": "test34-20190719165631320343-3b93ba",
      "dnis": "61412345679", "segment_num": 1, "http_status": 200 },
    { "message_id": "0232f882-8004-462b-95f6-ddfc685f72dc",
      "dnis": "61412345680", "segment_num": 1, "http_status": 500 }
  ]
}
HTTP API
Submit and query SMS with simple URL requests
https://api1.intracent.com:8002/api

Connecting

The HTTP API is for SMS submission and delivery status requests. Send requests with GET or POST. Your account manager supplies credentials for each new interconnection. Send them with every request: in the query string, in a JSON body (POST with Content-Type: application/json), or as a Basic Authorization header. Requests without them are rejected.

HTTPS (port 8002)
https://api1.intracent.com:8002/api (recommended)
HTTP (port 8001)
http://api1.intracent.com:8001/api
GET / POST /api?command=submit

Submit an SMS

To send to several numbers, put up to 100 comma-separated numbers in dnis. URL-encode every value in GET requests. Always send serviceType, even when it is empty.

username
string required
Login supplied by Intracent.
password
string required
Password supplied by Intracent.
command
string required
Request type. Use "submit" to send.
ani
string optional
Sender ID (caller ID). Alphanumeric, up to 32 characters. Some routes add their own limits.
dnis
string required
Destination number in international E.164 format, up to 15 digits. For several, comma-separate up to 100 numbers (2,048 characters). Duplicates are sent once.
message
string required
Message text. URL-encode it in GET requests.
serviceType
string required
Service type for your interconnection, given by Intracent. Send it even when empty (serviceType=). Up to 6 characters.
longMessageMode
string optional
cut (default), split, split_sar, single_id_split, payload or split_or_payload. See Long messages.
incMsgId
string optional
Your own message ID, up to 124 bytes, so you can trace a message even if it isn’t routed. Split parts get -1, -2 and so on.
validityPeriod
string optional
How long the network keeps trying, in SMPP format: relative (000002000000000R = 2 days) or absolute (261222080910000- = 22 Dec 2026, 08:09:10 UTC).
srcTon, srcNpi, dstTon, dstNpi
integer optional
TON/NPI values for ANI and DNIS.
dataCoding
integer optional
0 GSM default, 1 ASCII, 3 Latin-1, 6 Cyrillic, 7 Hebrew, 8 UCS2, 10 ISO-2022-JP, 14 KS C 5601. Leave it out and we choose GSM 7-bit or UCS2 from your text.
esmClass
integer optional
Same as the SMPP parameter. 0–255.
priorityFlag
integer optional
Same as the SMPP parameter. 0 or 1.
registeredDelivery
integer optional
Same as the SMPP parameter. 0 or 1.
replaceIfPresentFlag
integer optional
Same as the SMPP parameter. 0 or 1.
flash
integer optional
1 marks a flash message (shown on screen, not stored). The flag is recorded with the message and doesn’t change the data coding.
silent
integer optional
Set to 1 for a silent SMS: no sound and not shown on screen. Only 0 means not silent. Any other value, including "false", is treated as 1. Whether it arrives silent depends on downstream carriers.
command=submit · cURL
curl -G 'https://api1.intracent.com:8002/api' \
  --data-urlencode 'command=submit' \
  --data-urlencode 'username=<USERNAME>' \
  --data-urlencode 'password=<PASSWORD>' \
  --data-urlencode 'ani=Intracent' \
  --data-urlencode 'dnis=61412345678' \
  --data-urlencode 'message=Your code is 418209' \
  --data-urlencode 'serviceType=' \
  --data-urlencode 'longMessageMode=split'
200 OK · single recipient
{"message_id":"alss-a1b2c3d4-e5f67890"}
200 OK · multiple recipients or split message
[
  {"dnis":"61412345678","message_id":"5b4c46a8-8dc9-44b4-f55f-3bef56819305","segment_num":"1"},
  {"dnis":"61412345678","message_id":"5b4c46a8-46bc-7ee6-4a16-7d4e5a0d14af","segment_num":"2"}
]
Rejected
HTTP/1.1 400 Bad Request
NO ROUTES

HTTP/1.1 400 Bad Request
Destination number is too long

HTTP/1.1 401 Unauthorized
not authorized (check login and password)

Long messages

longMessageMode controls messages longer than one SMS. The default is cut, which drops everything after the first SMS, so send longMessageMode=split unless you are sure every message fits. Length is counted after URL decoding.

cut
Default. Sends only what fits in one SMS (140 bytes: 160 GSM or 70 Unicode characters) and drops the rest.
split
Recommended. Splits the message into segments with a UDH header, with one message_id per segment.
split_sar
Same as split, using SAR parameters instead of a UDH header.
single_id_split
Splits the message but returns one message_id. You get one report: DELIVRD when every part is delivered, the first failure otherwise, or EXPIRED after 48 hours if a part never reports.
payload
Sends the whole text in the message_payload field.
split_or_payload
For long messages on SMPP routes: sent in message_payload where the route supports it, otherwise split. One number per request.
GSM 7-bit (dataCoding 0, 1, 3)
Up to 160 characters in one SMS. Longer messages go in segments of 153. Leave dataCoding out and we use GSM 7-bit whenever every character fits.
Unicode UCS2 (dataCoding 8)
Up to 70 characters in one SMS. Longer messages go in segments of 67. Other codings (2, 4–7) fit 140 bytes, then 134 bytes per segment.
GET / POST /api?command=query

Query message status

Look up the status of a submitted message with its message_id. Statuses are kept for 24 hours after submission. All parameters are required.

username
string required
Login.
password
string required
Password.
messageId
string required
The message_id returned when you submitted the message.
command
string required
Must be "query".
command=query · cURL
curl -G 'https://api1.intracent.com:8002/api' \
  --data-urlencode 'command=query' \
  --data-urlencode 'username=<USERNAME>' \
  --data-urlencode 'password=<PASSWORD>' \
  --data-urlencode 'messageId=alss-a1b2c3d4-e5f67890'
200 OK
{"status": "DELIVRD", "delivery_time": "20260930042111", "mccmnc": "505001",
 "error_code": "000", "system_delivery_time": "260930042112"}
200 OK · not found, or older than 24 hours
{"status": "UNKNOWN", "delivery_time": "", "mccmnc": ""}

delivery_time is when the network delivered the message (YYYYMMDDHHMMSS, empty until a report arrives). error_code is the delivery error code. system_delivery_time is when Intracent received the report (YYMMDDHHMMSS). mccmnc is the E.212 network code. See message statuses.

WEBHOOK GET → your endpoint

Delivery receipts

Give us an HTTPS URL and Intracent calls it with a GET request for every delivery report, with the fields below in the query string. You choose the parameter names: we set up your callback template when you go live. Match reports to sent messages with msg_id, the ID the submit response returned. More fields are available on request: mccmnc, network and country name, price, and Unix timestamps.

msg_id
The message_id the submit response returned.
state
Delivery status. See Message statuses.
reason_code
Delivery error code from the network. 000 when delivered.
from
Recipient number of the SMS.
to
Sender ID used for the SMS.
time
Delivery time reported by the network (YYYY-MM-DD HH:MM:SS).
mcc
Country code of the recipient’s network (E.212).
mnc
Network code of the recipient’s network (E.212).
part_amount
Number of segments the message was split into.
GET https://[your-endpoint]
GET https://your-app.example.com/sms/dlr
  ?msg_id=alss-a1b2c3d4-e5f67890
  &state=DELIVRD
  &reason_code=000
  &from=61412345678
  &to=Intracent
  &time=2026-09-30%2004%3A21%3A11
  &mcc=505
  &mnc=01
  &part_amount=1
WEBHOOK GET → your endpoint 2-way SMS

Inbound (MO) messages

Replies from end users (mobile-originated messages) reach you the same way as delivery reports: as GET requests to an HTTPS URL you give us, with the parameter names you choose. Over SMPP they arrive on your bind as deliver_sm.

msg_id
Unique Intracent ID for the reply.
message
Reply text, UTF-8.
from
Phone number of the person who replied.
to
Your number the reply was sent to.
time
When Intracent received the reply (YYMMDDHHMMSS).
mt_msg_id
The message_id of your SMS this is a reply to, when known.
GET https://[your-endpoint]
GET https://your-app.example.com/sms/inbound
  ?msg_id=alss-9f8e7d6c-b5a41230
  &message=C
  &from=61412345678
  &to=61480012345
  &time=260930042502
  &mt_msg_id=alss-a1b2c3d4-e5f67890
SMPP
Carrier-grade binds for high-throughput traffic

Connecting over SMPP

SMPP suits aggregators, carriers and high-volume senders that need persistent connections and low latency. Delivery receipts and inbound (MO) messages come back over the same bind, so it supports 1-way and 2-way traffic.

Connection
SMPP 3.4. Bind as transceiver, transmitter or receiver. Your account manager sets up the host, system_id and password.
Ports
2875, or 2876 for TLS. We accept binds only from the IP addresses you register with us.
Messaging
Submit MT messages. Get delivery receipts and inbound MO messages on the same bind.
Parameters
Standard SMPP fields (data_coding, esm_class, priority_flag, registered_delivery, validity_period, TON/NPI). service_type is up to 6 characters. The HTTP API takes the same fields.
Reporting
EDRs, invoices and statistics are at portal.intracent.com.

SMPP error codes

0x00000000
ESME_ROK: accepted
0x00000045
ESME_RSUBMITFAIL: no route for this message, or the route timed out
0x00000014
ESME_RMSGQFUL: your throughput limit is full. Retry shortly
0x00000058
ESME_RTHROTTLED: too many messages per second. Slow down and retry
0x0000000D
ESME_RBINDFAIL: bind refused. Check system_id, password and system_type
0x00000005
ESME_RALYBND: too many sessions open for this account
0x00000004
ESME_RINVBNDSTS: command not allowed in the current bind state
err:000 / err:001
In delivery receipts: 000 = delivered; 001 = undeliverable because no route was available or it was rejected. Other codes come from the network.
Need an SMPP bind? Send us the IP addresses you will connect from, and your account manager sets up the host and credentials. Request SMPP access
HLR / MNP
Number query: validity, network and portability
http://hlr.intracent.com:42081/hlr/mccmnc_request
GET /hlr/mccmnc_request

Query a number

Find the network (MCC/MNC) that serves a number now, and whether it has been ported, before you send. Contact the Intracent support team for access. Carriers can also query over ENUM (DNS NAPTR, port 5053).

login
string required
Username supplied by Intracent.
password
string required
Password supplied by Intracent.
dnis
string required
Number to look up, in international E.164 format.
message_id
string optional
Your own request ID, returned when enabled. Handy for troubleshooting.
sender_id
string optional
The sender ID you plan to use.
noCache
1 optional
Set to 1 to skip cached results and query the network now.
Response fields
mccmnc
Mobile Country Code + Mobile Network Code of the network serving the number now (6 digits).
result
0 = success. Negative values are listed under result codes.
ported
1 if the number has been ported, 0 if not.
source_name
Name of the lookup source that answered.
source_type
Type of that source, e.g. hlr or mnp.
dnis
The number that was looked up.
login
Your login.
On request
cached, rate, message_id, present, roaming, providerResponseCode, system_response_code and message.
GET /hlr/mccmnc_request · cURL
curl -G 'http://hlr.intracent.com:42081/hlr/mccmnc_request' \
  --data-urlencode 'login=<LOGIN>' \
  --data-urlencode 'password=<PASSWORD>' \
  --data-urlencode 'dnis=61468451461'
200 OK
{
  "mccmnc": "505003",
  "result": 0,
  "ported": 1,
  "source_name": "hlr_primary",
  "source_type": "mnp",
  "dnis": "61468451461",
  "login": "your_login"
}

HLR result codes

These are the values of result. Any negative value means no network was found, so treat the number with care. Ask us to add system_response_code (0 to 3) or the provider's own providerResponseCode to your responses.

0
Success: the network serving the number was found
-1
The lookup answered, but without a network for this number
-2
No lookup rule covers this number, or the number is too long
-3
No valid network found (an empty answer, or an unknown error code)
-4, -6, -7
Timeout. Try again
-5
The number is blacklisted
-10
The network returned isn’t in our reference data

Message statuses

These are returned by status queries and in the state field of delivery receipts.

ENROUTE
In routing, or sent to the network and waiting for a delivery report
ACCEPTD
Accepted by the network (SMSC)
DELIVRD
Delivered to the handset
EXPIRED
The validity period ran out before delivery
DELETED
Deleted by the network
UNDELIV
Can’t be delivered
REJECTD
Rejected by the network, or by Intracent, e.g. no route available
UNKNOWN
Status unknown, or no longer held (statuses are kept for 24 hours)

HTTP responses

HTTP API
200 OK
Processed. The body has the message_id or status.
400 Bad Request
Rejected. The body gives the reason: NO ROUTES, Destination number is too long, or Service type is invalid.
401 Unauthorized
not authorized (check login and password).
508 Loop Detected
The message looped between networks and was stopped.
REST API (the body is JSON with an error_message)
200 OK
Processed.
400 Bad Request
A required parameter is missing: "Parameter … required". Also returned when a message can’t be routed.
401 Unauthorized
"Authorization failed": wrong login or password.
404 Not Found
The /rest path is wrong.
405 Method Not Allowed
"Request … unsupported": the method name is wrong.
426 Upgrade Required
"Token is expired", or the token is used from another IP address. Get a new token.
500 Internal Server Error
Usually a badly formed parameter. Check the request, then contact support.

Need help integrating?

Email support@intracent.com for credentials, SMPP binds, HLR access or integration questions.