Skip to content
  • There are no suggestions because the search field is empty.

InteractSMS V2 API - OAUTH

This guide will show you details of our new OAUTH API! Please reach out to sales@phonovation.com to get setup!

🔐 Authentication – Getting Your Access Token

To interact with the InteractSMS API, you must first obtain a JWT access token using the Auth API.

📌 Do Not Change client_id or grant_type

Important:
When requesting a token, you must always send:

  • client_id=ismstoken
  • grant_type=password

These two values must remain exactly as shown. Only change the username and password fields.

🔑 Auth API Endpoint

POST https://auth.interactsms.com/token

Required Headers

  • Content-Type: application/x-www-form-urlencoded

Request Body Example

grant_type=password
username=your_username
password=your_strong_password
client_id=ismstoken

Example Success Response

{
  "access_token": "eyJhbGciOi...",
  "expires_in": 120,
  "refresh_token": "eyJhbGciOi...",
  "token_type": "Bearer"
}

Authentication Header Example

Authorization: Bearer YOUR_ACCESS_TOKEN
📤 Sending a Campaign – InteractSMS API

Once authenticated, you can send SMS campaigns using the InteractSMS API.

POST https://api.interactsms.com/api/v2/Campaign

Header

  • Authorization: Bearer {access_token}

Basic Campaign Payload

{
"text": "Come check out v2 of our API!!",
"from": "Phonovation",
"recipientInfo": [
{
"msisdn": "35386xxxxxxx"
}
]
}

Future Campaign Payload

{
"text": "Come check out v2 of our API!!",
"from": "Phonovation",
"recipientInfo": [
{
"msisdn": "35386xxxxxxx"
}
],
"sendAt": "2030-03-28T20:00Z"
}

Basic campaign with multiple Recipients and NotifyID

{
"text": "Come check out v2 of our API!!",
"from": "Phonovation",
"recipientInfo": [
{
"msisdn": "35386xxxxxxx",
"notifyId": "user-123"
},
{
"msisdn": "35387xxxxxxx",
"notifyId": "user-987"
}
]
}

Success Response

{
  "success": true,
  "message": "Campaign scheduled",
  "errors": []
}
✅ API Health Check

GET https://api.interactsms.com/health
Response: 200 OK