API 2.2 and Earlier Versions - Discontinued
All versions prior to 2.3.0 were permanently shut down on December 31, 2025
API Documentation
Integrate JDI's powerful voice messaging services into your applications
JDI REST API v2.3.0 Overview
JDI provides a RESTful API for programmatic access to voice messaging, IVR, and communication services. The current version is API 2.3.0. All previous versions (2.2 and earlier) were permanently discontinued on December 31, 2025.
Base URL
https://api.23.rvmpro.com
Authentication
All API requests require a Bearer token in the Authorization header: Authorization: Bearer YOUR_API_KEY
Request Format
All requests and responses use JSON format with Content-Type: application/json
Available API Resources
- Campaigns — Create, read, update, and delete voice messaging campaigns (POST /campaigns, GET /campaigns/:id, PUT /campaigns/:id, DELETE /campaigns/:id)
- Contacts — Manage contact lists and recipients for campaigns
- Audio — Upload and manage audio files for voice messages
- IVR — Configure Interactive Voice Response systems and call flows
- Numbers — Manage virtual phone numbers and SmartPool number rotation
- Reports — Access campaign analytics, delivery reports, and performance data
- Account — Manage account settings, billing, and API keys
Interactive Documentation
Full interactive API documentation with try-it-out capability is available via Swagger UI at https://api.23.rvmpro.com/api/docs
Migration from API 2.2
Key changes: Base URL changed from api.22.rvmpro.com/campaigns to api.23.rvmpro.com. Authentication changed from form data token to Bearer token header. Request format changed from form-encoded to JSON. Endpoints changed from single-endpoint with action parameters to RESTful resource-based routes.
Support
For API integration help, contact support at 1-877-786-9603 or email sales@justdeliverit.net.
Current API Version - 2.3.0
This is the latest and actively maintained API version. All new integrations should use API 2.3.0.
Auto-Synced: This documentation automatically updates when API changes are deployed.
Legacy API - Discontinued December 31, 2025
API 2.2 and all previous versions have been permanently discontinued.
Action Required: Please migrate to API 2.3.0 immediately. Legacy endpoints are no longer operational.
API 2.2 Documentation
Getting Started
🔑 Authentication
All API requests require your API key in the request body:
🌐 Base URL
All endpoints are relative to:
Example Request
curl -X POST https://api.22.rvmpro.com/campaigns \ -d "api=overview" \ -d "token=YOUR_API_KEY" \ -d "c_campaign_id=0000000001"
🚫 API 2.2 has been shut down
This API version is no longer operational. Please refer to the Migration Guide tab for step-by-step instructions on migrating to API 2.3.0.
Migration Guide: API 2.2 → API 2.3.0
Follow this guide to transition from the discontinued API 2.2 to API 2.3.0.
Complete Migration Checklist
🗓️ Migration Timeline
December 31, 2025 - Completed
API 2.2 and earlier versions have been permanently shut down
Now - Migrate Immediately
Update your integration to API 2.3.0 and test in development
Deploy to Production
Roll out your updated integration and verify all endpoints
🔄 Key Changes in API 2.3.0
1. Base URL Changed
Old (API 2.2)
New (API 2.3.0)
2. RESTful Endpoints
API 2.3.0 uses standard RESTful design with proper HTTP methods and resource paths.
# Old: Single endpoint with action parameter POST /campaigns?api=create # New: Resource-based endpoints POST /campaigns GET /campaigns/:id PUT /campaigns/:id DELETE /campaigns/:id
3. Authentication Method
Use Bearer token in Authorization header instead of form data.
Old Method
New Method
4. JSON Request/Response
All requests and responses now use JSON format instead of form-encoded data.
Content-Type: application/json
{
"trackName": "Customer Service",
"number": "8005551234"
}📝 Step-by-Step Migration
Update Base URL
Change all API calls to use https://api.23.rvmpro.com
Update Authentication
Move token to Authorization header with Bearer prefix
Update Content-Type
Set Content-Type: application/json for all requests
Update Request Format
Convert form data to JSON request bodies
Update Endpoints
Map old action parameters to new RESTful endpoints
Test in Development
Thoroughly test all integrations in dev environment
Deploy to Production
Roll out changes to production with monitoring
Remove Old Code
Clean up API 2.2 code after successful migration
Need Migration Help?
Our support team is ready to assist with your migration. We can provide code examples, answer questions, and help troubleshoot issues.
Developer Support
Our team is here to help you succeed with the JDI API.