For Agents
Programmatically send automated sms campaign message. Covers 1 operations with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RooR SMS API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with RooR SMS API.
Send automated SMS campaign message
Manage communications data programmatically
Integrate RooR SMS API into automated workflows
Query and filter RooR SMS API records by parameters
GET STARTED
Use for: I need to send automated sms campaign message, Find available communications operations, Get the current status of RooR SMS API resources, List all records from RooR SMS API
Not supported: Does not handle payments, crm, or developer tools — use for communications only.
RooR SMS API for sending automated campaign SMS messages with recipient management. The API exposes 1 endpoints secured with apiKey authentication.
Monitor RooR SMS API operational status and events
Patterns agents use RooR SMS API for, with concrete tasks.
★ Communications Operations
Use the RooR SMS API to perform communications operations programmatically. The API provides 1 endpoints covering core functionality including send automated sms campaign message.
Call POST /v2.0/api/post/autoCampaignSend/key/{api_key}/response/json/campaign/{campaign_id} to send automated sms campaign message
Data Retrieval and Monitoring
Query RooR SMS API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary RooR SMS API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call RooR SMS API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'send automated sms campaign message', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — roor sms api for sending automated campaign sms messages with recipient management.
METHOD
PATH
DESCRIPTION
/v2.0/api/post/autoCampaignSend/key/{api_key}/response/json/campaign/{campaign_id}
Send automated SMS campaign message
/v2.0/api/post/autoCampaignSend/key/{api_key}/response/json/campaign/{campaign_id}
Send automated SMS campaign message
Three things that make agents converge on Jentic-routed access.
Credential isolation
RooR SMS API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'send automated sms campaign message') and Jentic returns the matching RooR SMS API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct RooR SMS API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using RooR SMS API through Jentic.
What authentication does the RooR SMS API use?
The RooR SMS API uses an API key passed in the `api_key` path. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I send automated sms campaign message with the RooR SMS API?
Yes. Use the POST /v2.0/api/post/autoCampaignSend/key/{api_key}/response/json/campaign/{campaign_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the RooR SMS API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I send automated sms campaign message through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'send automated sms campaign message'. Jentic returns the matching RooR SMS API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the RooR SMS API have?
The RooR SMS API exposes 1 endpoints covering sms campaigns operations.