canonical: https://jentic.com/apis/quicksend.lk/quicksend-lk # Quicksend Lk QuickSend SMS API QuickSend is an SMS Gateway Solution for Sri Lanka. This API allows sending single and bulk SMS messages and checking account balance. The API exposes 4 endpoints secured with apiKey authentication. ## For AI agents Programmatically send a single sms, send bulk sms with same message. Covers 4 operations with apiKey authentication. ## Scope Does not handle payments, crm, or developer tools - use for communications only. ## Capabilities - Send a single SMS - Check account balance - Access QuickSend SMS API communications resources via REST API ## Use cases ### Communications Operations Use the QuickSend SMS API to perform communications operations programmatically. The API provides 4 endpoints covering core functionality including send a single sms, send bulk sms with same message, send bulk sms with different messages. Example prompt: Call GET /api.php to send a single sms ### Automated SMS Management Automate sms operations by combining multiple QuickSend SMS API endpoints. Agents can send bulk sms with same message and then send bulk sms with different messages in a single workflow. Example prompt: Call GET /api.php#sendBulkSame to send bulk sms with same message, then verify the result ### AI Agent Integration via Jentic AI agents discover and call QuickSend 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 a single sms', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api.php` | Send a single SMS | | GET | `/api.php#sendBulkSame` | Send bulk SMS with same message | | GET | `/api.php#sendBulkDifferent` | Send bulk SMS with different messages | | GET | `/api.php#checkBalance` | Check account balance | ## Key resources - **SMS** — Send SMS messages - **Account** — Account management operations ## 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:** 49 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 53 / 100 - Agent Usability: 94 / 100 - Security: 15 / 100 - AI Discoverability: 75 / 100 - **View full report:** https://jentic.com/apis/quicksend.lk/quicksend-lk/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 QuickSend SMS by hand means passing its up key as a query parameter, targeting the quicksend.lk/Client host, and handling retries across its send and balance operations yourself. Through Jentic you install once, import QuickSend SMS from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** QuickSend SMS drives sends and balance checks through query parameters on a single api.php endpoint, so limit the agent to the operations it needs, such as sending a single message or checking the balance. You choose which operations are allowed, so bulk sends are not reachable unless you add them. - **Credential handling:** Your QuickSend 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 SMS message' or 'check SMS balance', and Jentic returns the matching QuickSend 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 QuickSend SMS API use? The QuickSend SMS API uses an API key passed in the `up` query. 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 a single sms with the QuickSend SMS API? Yes. Use the GET /api.php endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the QuickSend 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 a single sms through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send a single sms'. Jentic returns the matching QuickSend SMS API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the QuickSend SMS API have? The QuickSend SMS API exposes 4 endpoints covering sms, account operations. ### Can I limit what my agent is allowed to do with the QuickSend SMS API? Yes. Because you run Jentic One yourself, your own rules decide which QuickSend SMS operations the agent may call and which credentials it may use. QuickSend drives every action through query parameters on a single api.php endpoint, so you can allow just sending a single message or checking the account balance and leave the bulk-send operations out entirely. Bulk sends stay unreachable unless you explicitly add them, and your API key is injected only for the calls you have approved.