LogoLogo
cegedim.cloudITCareAPIPrivacy
English
English
  • Documentation
  • ITCare
    • What is ITCare ?
      • Get started with ITCare
      • Demos
    • Enercare
      • Carbon footprint
    • Release notes
  • ITCare API
    • Overview
    • Authentication
    • Errors
    • Pagination
    • API Reference
      • Quick start
      • Analytics
        • Matomo
      • Changes
        • Changes
      • Compute
        • Application Servers
        • Backup Policies
        • Containers
        • Environments
        • Instances
        • Platform
        • Resource Filters
        • Resource Types
        • Resources
        • Services
        • Statuses
        • Tag Keys
        • Tag Values
        • Types
      • Databases
        • Databases
        • MariaDB
        • OpenSearch
        • PostgreSQL
        • Redis
        • SQL Server
      • Hardwares
        • Hardwares
      • Messaging
        • Apache Kafka
        • Message Brokers
        • RabbitMQ
      • Networking
        • Domains
        • Load Balancers
        • Network Clusters
        • Networks
      • Operations
        • Actions
        • Operations
      • Storage
        • Glusterfs
        • Overdrive
      • Topology
        • Topology
  • Services
    • Products
    • Support policy
    • Patch policy
    • RACI
  • Analytics
    • Matomo
      • Matomo - Features
      • Matomo - Get started
  • Compute
    • Virtual instances
      • Virtual instances - Features
        • Linux - Hardening
      • Virtual instances - Get started
    • Containers (K8s)
      • K8s - Features
        • Hardening
        • Persistent Storage
      • K8s - Get started
        • High Availability
  • Databases
    • MariaDB
      • MariaDB - Features
      • MariaDB - Get started
    • OpenSearch
      • OpenSearch - Features
        • v2 - Breaking changes
      • OpenSearch - Get started
    • PostgreSQL
      • PostgreSQL - Features
      • PostgreSQL - Get started
      • PostgreSQL - Upgrade
    • Redis
      • Redis - Features
      • Redis - Get started
      • Redis - Upgrade
    • SQL Server
      • SQL Server - Features
      • SQL Server - Get started
  • Messaging
    • Apache Kafka
      • Apache Kafka - Features
      • Apache Kafka - Get started
      • Apache Kafka - Upgrade
    • RabbitMQ
      • RabbitMQ - Features
      • RabbitMQ - Get started
    • SMS
      • SMS - Get started
  • Monitoring
    • ExtraHop
  • Security
    • Advanced Vulnerability Assessment
    • Bot Defense
      • Bot Defense - Features
    • Data Masking
      • Data Masking - Get started
    • Phishing Campaign
  • Storage
    • GlusterFS
      • GlusterFS - Features
      • GlusterFS - Get started
    • Object Storage
      • Object Storage - Features
        • S3 API compatibility
        • Limitation and Best Practices
        • Presigned URL
        • Bucket Policies
        • Bucket Lifecycle
        • Object Lock
      • Object Storage - Get started
        • Manage Object Users
        • Manage versioning in Bucket
        • Manage Bucket access
    • OverDrive
      • OverDrive - Features
      • OverDrive - Get started
Powered by GitBook
On this page
  • API Documentation
  • URL & Base URI
  • Security
  • HTTPS Protocol
  • Authentication
  • HTTP Request and Responses format : json
  • HTTP Request format
  • HTTP Response format
  • Date/Time format
  • Sender Name
  • Custom data
  • PUSH responses
  • Limits
Export as PDF
  1. Messaging
  2. SMS

SMS - Get started

PreviousSMSNextExtraHop

Last updated 1 month ago

API Documentation

API Swagger Documentation is available here :

URL & Base URI

Vortext API base path is located at :

All methods are relative to this URL.

For example if you want to get status of vortext, you have to use:

GET https://messages.cloud.cegedim.com/status

Security

HTTPS Protocol

All requests to Vortext API is made by HTTP protocol, using TLSv1 transport encryption.

Authentication

As for now, basic authentication is used for every request made to Vortext service. Each request is completely stateless, so you can use Vortext service with a simple line of curl. If you don’t know about basic authentication, it only needs a http request header 'Authorization' :

Authorization Basic YWRtaW5pc3RyYXRvc5cnF2NjBTenh3djRuaU5meEV5VFgwaUN4VmNTaHF1djBYU0RIbjY2

The credential used if username:password encoded in base 64. Most of libraries will simply let you provide username and password.

HTTP Request and Responses format : json

This API is aimed primarily to handle json messages in http request and response bodies.

HTTP Request format

Use Content-Type: application/json header to let Vortext service know your request body format.

HTTP Response format

Use Accept: application/json header to let Vortext service which format do you want for body response.

Date/Time format

As json doesn’t support natively Date/Time, all parameters tagged as Date in this API are string with ISO8601 format :

`YYYY-MM-DDTHH:MM:SS.sssZ`

where Z is timezone (like +0200).

Examples : 2016-06-01T12:27:19.000+0200.

For query parameters, don’t forget to url encode these parameters.

Sender Name

You can customize sender name of SMS, instead of a classic number such as "30180". To do so, please make a request in ITCare to our team by requesting this feature to be setup.

Once your account configured, all SMS sent will be with this sender name. As per now, it is not possible to have multiple sender name per account.

Custom data

Optionnaly, you can add a metadata object to sms send request, to tag custom data for this message. The added tag will be retrieved when getting the detail of the SMS.

Exemple of SMS sending with a metadata tag :

{ "phoneNumber": "+3361127272727", "message": "Please call me", "metadata": { "myCustomerId": "123de32", "caller": "MyApp 2.2" } }

PUSH responses

It is possible to receive PUSH responses (https REST call) as soon as a customer makes a response to a previously sent SMS. To activate this features, please make a request in ITCare to our team .

Here is the specifications of outbound request you will receive once activated :

Protocol

https

URL

<yours>

HTTP method

POST

Authentication

None

Content-Type

application/json

Message Body

{ "response": { "content": "Response of your customer", "answeredAt" : "2020-02-12T13:00:00.000+0000" }, "message": { }}

Limits

You can set limits to avoid multiple calls / bad loops and prevent some flooding :

  • total SMS sent by minute

  • total SMS sent by hour

To activate this features, please make a request in ITCare to our team.

for services hosted in cegedim.cloud datacenters.

for 3rd party applications reaching Vortext on the internet.

https://vortext.cloud.cegedim.com
https://messages.cloud.cegedim.com
https://apidocs.cegedim.cloud/swagger-ui/index.html?urls.primaryName=SMSapidocs.cegedim.cloud