canonical: https://jentic.com/apis/sms77.io/sms77

# Sms77 seven

seven.io offers you the possibility to send SMS, text2voice messages, perform home register lookups, mobile number portability status lookups, phone number formats and much more. The API exposes 20 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically get analytics, get balance. Covers 20 operations with oauth2 authentication.

## Scope

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

## Capabilities

- Get Analytics
- Lookup Caller Name
- Integrate seven into automated workflows
- Query and filter seven records by parameters
- Monitor seven operational status and events

## Use cases

### Communications Operations

Use the seven to perform communications operations programmatically. The API provides 20 endpoints covering core functionality including get analytics, get balance, get outbound messages.

Example prompt: Call GET /analytics to get analytics

### Automated sms Management

Automate sms operations by combining multiple seven endpoints. Agents can get balance and then get outbound messages in a single workflow.

Example prompt: Call GET /balance to get balance, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call seven 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 oauth2 tokens manually.

Example prompt: Search Jentic for 'get analytics', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /analytics | Get Analytics |
| GET | /balance | Get Balance |
| GET | /journal/outbound | Get outbound messages |
| GET | /journal/inbound | Get inbound messages |
| GET | /journal/replies | Get message replies |
| GET | /journal/voice | Get voice journal |
| GET | /lookup/cnam | Lookup Caller Name |
| GET | /lookup/format | Lookup Format |

## Key resources

- **sms** — Operations related to sms
- **balance** — Operations related to balance
- **pricing** — Operations related to pricing
- **status** — Operations related to status
- **validate_for_voice** — Operations related to validate_for_voice

## Why Jentic

- **Setup:** Wiring seven by hand means implementing its OAuth2 flow, pointing at the gateway.seven.io host, and adding your own retry handling around SMS, voice, and lookup calls. Through Jentic you install once, import seven from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** seven identifies work by operation rather than a resource id in the URL path, so limit the agent to the operations it needs, such as reading analytics or checking the account balance. You choose that set, so lookup or journal reads can be included while everything else stays out.
- **Credential handling:** Your seven OAuth2 credential 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 'get messaging analytics' or 'check account balance', and Jentic returns the matching seven 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 seven use?

The seven uses OAuth 2.0 for authorization. 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 get analytics with the seven?

Yes. Use the GET /analytics endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the seven?

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 get analytics through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get analytics'. Jentic returns the matching seven operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the seven have?

The seven exposes 20 endpoints covering sms, balance, pricing operations.

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

Yes. Because seven identifies each action by operation rather than by a resource id in the URL, your self-hosted Jentic One instance lets you decide exactly which operations the agent may call. You can grant it read-only work such as GET /analytics and GET /balance, or add lookup and journal reads like /lookup/cnam, /lookup/format, and /journal/outbound, while every other operation stays out of reach. Those rules are set by you as the operator, and the stored OAuth2 credential is only ever used for the operations you permit.