canonical: https://jentic.com/apis/roor.app/roor

# Roor App RooR SMS API

RooR SMS API for sending automated campaign SMS messages with recipient management. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically send automated sms campaign message. Covers 1 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- 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
- Monitor RooR SMS API operational status and events

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'send automated sms campaign message', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2.0/api/post/autoCampaignSend/key/{api_key}/response/json/campaign/{campaign_id}` | Send automated SMS campaign message |

## Key resources

- **SMS Campaigns** — Operations related to SMS Campaigns

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 57 / 100
  - Agent Usability: 94 / 100
  - Security: 0 / 100
  - AI Discoverability: 0 / 100
- **View full report:** https://jentic.com/apis/roor.app/roor/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the RooR SMS API by hand means placing your API key in the URL path on the campaign-send call and handling the request plumbing yourself. Through Jentic you install once, import the RooR SMS API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The RooR SMS API exposes a single campaign-send operation with the campaign id in the URL path, so limit the agent to just that send operation. You choose whether it may call it, and it can do nothing beyond what you allow.
- **Credential handling:** Your RooR SMS API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send an automated SMS campaign', and Jentic returns the matching RooR SMS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the RooR SMS API?

Yes. Jentic One is self-hosted, so you set the rules that decide which operations and credentials your agent may use. The RooR SMS API exposes only a single campaign-send operation, POST autoCampaignSend with the campaign id in the URL path, so you can allow the agent to trigger that send and nothing else. Your stored API key is injected at execution time and never enters the agent's prompt or context, and the agent can do nothing beyond the send call you permit.