46elks API
★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingbasic13 EndpointsREST
For Agents
Send and receive SMS and MMS, place phone calls, and manage virtual phone numbers via 46elks using HTTP Basic auth.
Use for: I want to send an SMS through 46elks, Place a voice call to a customer, List my recent outbound SMS messages, Send a picture message via MMS
Not supported: Does not handle email, push notifications, or chat platforms — use for SMS, MMS, voice calls, and virtual number management only.
Jentic publishes the only available OpenAPI specification for 46elks API, keeping it validated and agent-ready. The 46elks API lets applications send and receive SMS, MMS, and voice calls and manage virtual phone numbers from a Nordic-focused communications provider. Authentication is HTTP Basic with the account API username and password. The 13 endpoints cover SMS, MMS, calls, numbers, and account information.
Install Jentic One Beta
Connect the 46elks API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 46elks 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.
1
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 | sh2
Step 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.
Capabilities
What an agent can do with 46elks API.
Send outbound SMS messages to any international number using POST /sms
Send MMS messages with image or media attachments via POST /mms
Place outbound voice calls and control flow with the calls endpoint
List and retrieve historical SMS messages and call records by ID
Provision and manage virtual phone numbers across supported countries via the numbers endpoints
Retrieve account balance and metadata via GET /me
Use Cases
Patterns agents use 46elks API for, with concrete tasks.
★ Two-Factor Authentication SMS
Send one-time codes for login or transaction verification via 46elks SMS. POST /sms accepts a sender alpha-tag, a recipient in international format, and a message body. The response carries a message ID that can be reconciled later via GET /sms/{smsId} for delivery tracking.
Send an SMS to +46701234567 with body 'Your code is 482917' from sender 'AcmeApp' via POST /sms and capture the returned message ID.
Outbound Voice Call Notifications
Place automated voice calls for high-priority alerts that SMS or email might miss, such as on-call escalations or appointment reminders. POST /calls initiates the call; the body specifies the recipient and the call flow (text-to-speech or audio URL). GET /calls/{callId} returns the call's outcome.
Place an outbound call to +46701234567 with a text-to-speech message announcing a Sev1 incident, capture the call ID, and poll its outcome.
MMS Picture Messaging
Send picture messages such as receipts, ID confirmations, or order updates by referencing an image URL in POST /mms. This is useful where a screenshot or visual confirmation conveys more than text and the recipient's carrier supports MMS.
Send an MMS to +46701234567 with the image at https://example.com/receipt.png and caption 'Your receipt for order #42' using POST /mms.
Agent-Driven Multichannel Notifications
Let an AI agent choose between SMS, MMS, and voice call based on the message type and route through Jentic. The agent searches by intent, loads the schema, and supplies recipient and content; HTTP Basic credentials stay isolated in Jentic's vault.
Through Jentic, search 'send an sms', load the 46elks POST /sms schema, and send a confirmation SMS to a recipient list.
Key Endpoints
13 endpoints — jentic publishes the only available openapi specification for 46elks api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/sms
Send an SMS message
GET
/sms/{smsId}
Retrieve a single SMS
POST
/calls
Place an outbound voice call
POST
/mms
Send an MMS picture message
GET
/numbers
List virtual phone numbers
GET
/me
Get account balance and metadata
POST
/sms
Send an SMS message
GET
/sms/{smsId}
Retrieve a single SMS
POST
/calls
Place an outbound voice call
POST
/mms
Send an MMS picture message
GET
/numbers
List virtual phone numbers
GET
/me
Get account balance and metadata
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
46elks HTTP Basic credentials are stored encrypted in the Jentic vault. Agents call /sms, /mms, and /calls through Jentic, which injects the Authorization: Basic header at execution — the raw credentials never enter the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g., 'send an sms' or 'place a phone call') and Jentic returns the matching 46elks operation with its input schema, so the agent calls the right endpoint without reading 46elks.com/docs.
Time to first call
Direct 46elks integration: 1 day to wire up Basic auth, payload shaping, and webhook handling. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using 46elks API through Jentic.
Why is there no official OpenAPI spec for 46elks API?
46elks publishes HTML reference docs at 46elks.com/docs but no OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call 46elks API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the 46elks API use?
It uses HTTP Basic authentication with your 46elks API username and password as documented at 46elks.com/docs. Through Jentic, the credentials are stored encrypted in the vault and injected into the Authorization header at execution.
Can I send MMS picture messages with 46elks?
Yes. POST /mms accepts a recipient and an image URL plus optional caption, and returns a message ID. MMS delivery requires the recipient's carrier and device to support MMS; otherwise the message may be returned as a text fallback.
Can I provision virtual phone numbers through the API?
Yes. The Numbers endpoints (GET /numbers and GET /numbers/{numberId}) let you list available and currently allocated numbers. Provisioning and termination are also handled via the same Numbers resource.
How do I send an SMS with 46elks through Jentic?
Run pip install jentic, then search 'send an sms', load the 46elks POST /sms operation, supply the from, to, and message fields, and execute. Sign up at https://app.jentic.com/sign-up to receive an agent API key for execution.
How do I check my 46elks account balance?
Call GET /me. The response includes the account balance and currency along with account metadata, which is useful before launching a high-volume campaign.
GET STARTED