|
|
|
|
|
|
|
|
If you prefer your mobile communications integrated
into your existing system, you can use the Dynmark SDK including Web Services,
HTTP Services or SMPP
Web Services
Looking to integrate messaging into an existing application? Our Web Services
should meet your requirements.
MORE INFO
HTTP Services
Our HTTP Services are ideal
for those who do not want to develop a whole application but would like to extend
their messaging functionality further, simply by entering a URL.
MORE INFO
SMPP 3.4
This is the mobile network operator's interface of choice, meaning that if you have
already invested in an SMPP connection to another operator or aggregator, it will
work perfectly with us too. MORE INFO
Inbound Messages
If you're looking for an easy way to receive Inbound Messages or Message Receipts, without
having to waste valuable server resources, Dynmark can forward these to you via HTTP.
MORE INFO
Phone Number Validation
Do you need to check whether a phone number is valid and assigned to an active handset?
Our phone number validation service can help.
MORE INFO
|
|
- WEB SERVICES
- HTTP SERVICES
- SMPP 3.4
- INBOUND MESSAGES / RECEIPTS
- PHONE NUMBER VALIDATION
Web Services
Our most popular integration option provides
a selection of the most commonly requested messaging services through an easy-to-use
SOAP compliant interface.
For more information see:
Before deciding which route to take towards integrating with our messaging services,
we suggest that you discuss your project and integration requirements with a member
of our technical team; email
SDK Support.
To use any of these services you will need to create a Dynmark Direct account. This
can be done by registering here, free of charge.
HTTP Services
Looking to integrate Messaging services into an existing application but cannot
use SOAP web services?
The HTTP Services are for those who need a simple messaging service using standard
HTTP protocol alone to operate it.
The HTTP interface allows the easy additon of basic messaging to an application
by simply entering a URL.
For more information regarding our HTTP Services and / or to download the documentation, please email
SDK Support.
SMPP 3.4
This is the mobile operator's interface protocol of choice. The standard interface
means that if you have already invested in an SMPP connection to another aggregator
or operator, you can use the Dynmark SMPP connection as well.
For more information email
SDK Support.
Inbound Messages / Receipts
If you're looking for an easy way to receive Inbound Messages or Message Receipts, without
having to waste valuable server resources, Dynmark can forward these to you via HTTP.
By simply informing us to what URL you would like Inbound Messages to send to, we'll add this
to your dedicated longnumber or shortcode, you configure the URL parameters to handle the
message and that's it! Once an Inbound Message is received, the Dynmark Messaging Platform forwards
the message to the specified URL immediately. This means messages aren't queued up or sent in a batch,
but are sent asynchronously so that messages are received in a real-time manner.
By combining the use of the Dynmark Web Services, you can specify a URL to post back to when
the messages you send have received a receipt. The Dynmark Messaging Platform then looks up
the URL and send the receipt back to the address you specified. Receipts are forwarded
asynchronously, meaning message receipt will be updated as the receipts are processed, not
in the order the messages were sent in.
For more information regarding HTTP forwarding and / or to
download the documentation, email
SDK Support.
Phone Number Validation Service
Our phone number validation service
combines number format validation and a handset status check in one simple
SOAP call.
For more information see:
To use this service please contact our sales team to activate it on your Dynmark Direct account.
|
|
|
|
|