CM API Docs

Bulk SMS

CM's Bulk SMS Gateway enables you to send text messages to mobile phones all around the world in very high volume. To integrate this functionality into your application, you (or your developers) should implement communication with our API. The Bulk SMS Gateway API covers the interface between your application and the CM Platform by means of the HTTP protocol. Only bulk (free of charge for the end user) text messages are supported.

To the docs

Conversions

The purpose of the Conversion web api is to enable the third party to deliver conversion details per message to CM. A conversion is a confirmation by a third party that their end-user has used the contents of the sms/voice/push message that was processed by CM. Credentials will be provided by your account manager

To the docs

Hybrid Messaging

With Hybrid Messaging you are able to deliver messages to any phone number via SMS or Push. When the end users phone number has your app or our free Notifire app installed, the platform can deliver your message via push which is 50% of the SMS price. If the end user on the phone number does not have your app or Notifire installed, the message will automatically be send as an SMS.

To the docs

Idin

iDIN is a service by the banks, that allows customers to identify themselves with websites, using the same secure methods as their own bank uses. It is similar to the iDEAL system in how it works and operates. In addition to identification, it can also provide the connecting website with information about name, address and age of the consumer, if the consumer agrees to provide these. CM provides a simple API to integrate these options into your website. How does it work ? The merchant asks the customer to select his bank Start the request for authentication/information The customer is redirected to this bank The customer logs into his bank and approves the transaction The bank sends the customer back to the merchants (your) landing page The merchant rejoins the customer to his session and retrieves the transaction. You check with the CM iDIN system if the transaction was successful and receive the requested customer information. If you are curious about how your consumers would be using iDIN, then you can experiment with CM's iDIN demonstration. Remarks This API is preliminary. Changes might follow and simplified higher level API's will likely be developed, based on customer and pilot feedback. Additional security restrictions on the API might follow. The iDIN system currently is still in a pilot phase. That means you should not depend on it just yet. Usage The iDIN system allows you to service several use cases Checking if someone is known with a bank. To see if the user is a legal entity known to a bank To be able to trace the user in case of fraud. Being guaranteed that this is always the same person. For instance: To log a user into your system To avoid people registering multiple (fake) accounts in your system. To check if a user is above a certain age limit Retrieving name, address and age information of that person. You should always allow the user to override or change this information, because it is not guaranteed that the information is always correct or complete (someone could have moved but not yet have informed his bank). Match this against your own information and trigger audit signals Things you should not do: Matching an account in your system on the basis of name/address attributes. Either create a new account after user identified with iDIN or have the user log into your system before coupling with an iDIN identity Visual style There is a visual style that you are required to follow when using the iDIN brand.

To the docs

Number Verifier

The NumberValidation API validates any phonenumber. It will tell you the formatting options and type of the number, and will determine the most likely carrier.

To the docs

Payments

CM payments offers a solution for online payment transactions. The system supports several payment methods eg iDEAL, Credit Cards, Afterpay and Bancontact.

To the docs

Sms Campaign

SMS Campaign API

To the docs

Voice API

The Voice API is a system that enables you to easily write IVR (Interactive Voice Response) applications without setting up complicated telephone systems. The Voice API is actually not a web API, but rather a client, as it will call your server to inform it of updates and ask for the next step(s) to perform. The Voice API server will call your http(s) server using a POST command and it will send JSON data containing information on a new incoming call, a newly setup outgoing call (not supported yet) or a status update on a call (done playing audio file for instance). Your server will have to acknowledge this new information and reply with the next steps, such as "play an audio file", "make a voice recording" or "get DTMF (number) input". When the Voice API has performed these steps, it will again contact your server with updates on these steps and your server will again give it the next step(s), etc. Only when the Voice API sends a "disconnected" message will it not be expecting a new step to take, it will just expect a 200 - OK message.

To the docs