canonical: https://jentic.com/apis/text2vip.messagingchannel.com/text2vip-messagingchannel # Text2vip Messagingchannel Text2VIP API API for SMS and messaging services. The API exposes 2 endpoints secured with apiKey authentication. ## For AI agents Programmatically send an sms message, update subscription. Covers 2 operations with apiKey authentication. ## Scope Does not handle payments, crm, or developer tools - use for communications only. ## Capabilities - Send an SMS message - Update subscription - Integrate Text2VIP API into automated workflows - Query and filter Text2VIP API records by parameters - Monitor Text2VIP API operational status and events ## Use cases ### Communications Operations Use the Text2VIP API to perform communications operations programmatically. The API provides 2 endpoints covering core functionality including send an sms message, update subscription. Example prompt: Call POST /messages to send an sms message ### Data Retrieval and Monitoring Query Text2VIP 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 Text2VIP API endpoint, compare response to last known state, and alert if changed ### AI Agent Integration via Jentic AI agents discover and call Text2VIP 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 an sms message', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/messages` | Send an SMS message | | PUT | `/subscriptions` | Update subscription | ## Key resources - **messages** — Operations related to messages - **subscriptions** — Operations related to subscriptions ## 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:** 66 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 90 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 47 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/text2vip.messagingchannel.com/text2vip-messagingchannel/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 ``` ## Why Jentic - **Setup:** Wiring the Text2VIP API by hand means learning its Authorization header API-key auth against the api.text2vip.messagingchannel.com host and coding its message and subscription calls yourself. Through Jentic you install once, import the Text2VIP API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** Text2VIP carries the recipient and message in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as sending a message. You choose the operations it may call, so updating a subscription is not included unless you add it. - **Credential handling:** Your Text2VIP 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 SMS message', and Jentic returns the matching Text2VIP API 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 Text2VIP API use? The Text2VIP API uses an API key passed in the `Authorization` header. 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 an sms message with the Text2VIP API? Yes. Use the POST /messages endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Text2VIP 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 an sms message through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send an sms message'. Jentic returns the matching Text2VIP API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Text2VIP API have? The Text2VIP API exposes 2 endpoints covering messages, subscriptions operations. ### Can I limit what my agent is allowed to do with the Text2VIP API? Yes. Because you run Jentic One yourself, you decide which Text2VIP operations the agent may call, so you can allow it to send a message with POST /messages while withholding the ability to update a subscription with PUT /subscriptions. Text2VIP carries the recipient and message in the request body rather than a resource id in the URL, so restricting the agent to only the operations it needs keeps its access tightly scoped. Your API key is held and injected by your own instance under your rules, so the agent never sees the raw secret and can only run the calls you have permitted.