Telnyx Messaging Java Agent Skill

by team-telnyx

>- Send and receive SMS/MMS, handle opt-outs and delivery webhooks. Use for notifications, 2FA, or messaging apps.

11k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

201

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/team-telnyx/ai --skill telnyx-messaging-java

The instruction itself

23 sections, as written by the author

Telnyx Messaging - Java

Installation

<!-- Maven -->
<dependency>
    <groupId>com.telnyx.sdk</groupId>
    <artifactId>telnyx</artifactId>
    <version>6.82.0</version>
</dependency>

// Gradle
implementation("com.telnyx.sdk:telnyx:6.82.0")

Setup

import com.telnyx.sdk.client.TelnyxClient;
import com.telnyx.sdk.client.okhttp.TelnyxOkHttpClient;

TelnyxClient client = TelnyxOkHttpClient.fromEnv();

All examples below assume client is already initialized as shown above.

Error Handling

All API calls can fail with network errors, rate limits (429), validation errors (422),

or authentication errors (401). Always handle errors in production code:

import com.telnyx.sdk.models.messages.MessageSendParams;
import com.telnyx.sdk.models.messages.MessageSendResponse;
MessageSendParams params = MessageSendParams.builder()
    .to("+18445550001")
    .from("+18005550101")
    .text("Hello from Telnyx!")
    .build();
MessageSendResponse response = client.messages().send(params);

Common error codes: 401 invalid API key, 403 insufficient permissions,

404 resource not found, 422 validation error (check field formats),

429 rate limited (retry with exponential backoff).

Important Notes

Phone numbers must be in E.164 format (e.g., +13125550001). Include the + prefix and country code. No spaces, dashes, or parentheses.
Pagination: List methods return a page. Use .autoPager() for automatic iteration: for (var item : page.autoPager()) { ... }. For manual control, use .hasNextPage() and .nextPage().

Operational Caveats

The sending number must already be assigned to the correct messaging profile before you send traffic from it.
US A2P long-code traffic must complete 10DLC registration before production sending or carriers will block or heavily filter messages.
Delivery webhooks are asynchronous. Treat the send response as acceptance of the request, not final carrier delivery.

Reference Use Rules

Do not invent Telnyx parameters, enums, response fields, or webhook fields.

If the parameter, enum, or response field you need is not shown inline in this skill, read references/api-details.md before writing code.
Before using any operation in ## Additional Operations, read the optional-parameters section and the response-schemas section.
Before reading or matching webhook fields beyond the inline examples, read the webhook payload reference.

Core Tasks

Send an SMS

Primary outbound messaging flow. Agents need exact request fields and delivery-related response fields.

client.messages().send() — POST /messages

|-----------|------|----------|-------------|

| to | string (E.164) | Yes | Receiving address (+E.164 formatted phone number or short co... |

| ... | | | +7 optional params in references/api-details.md |

import com.telnyx.sdk.models.messages.MessageSendParams;
import com.telnyx.sdk.models.messages.MessageSendResponse;

MessageSendParams params = MessageSendParams.builder()
    .to("+18445550001")
    .from("+18005550101")

    .text("Hello from Telnyx!")
    .build();
MessageSendResponse response = client.messages().send(params);

Primary response fields:

response.data.id
response.data.to
response.data.from
response.data.text
response.data.sentAt
response.data.errors

Send an SMS with an alphanumeric sender ID

Common sender variant that requires different request shape.

client.messages().sendWithAlphanumericSender() — POST /messages/alphanumeric_sender_id

|-----------|------|----------|-------------|

| to | string (E.164) | Yes | Receiving address (+E.164 formatted phone number or short co... |

import com.telnyx.sdk.models.messages.MessageSendWithAlphanumericSenderParams;
import com.telnyx.sdk.models.messages.MessageSendWithAlphanumericSenderResponse;

MessageSendWithAlphanumericSenderParams params = MessageSendWithAlphanumericSenderParams.builder()
    .from("MyCompany")
    .messagingProfileId("182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e")
    .text("Hello from Telnyx!")
    .to("+13125550001")
    .build();
MessageSendWithAlphanumericSenderResponse response = client.messages().sendWithAlphanumericSender(params);

Primary response fields:

response.data.id
response.data.to
response.data.from
response.data.text
response.data.sentAt
response.data.errors

Webhook Verification

Telnyx signs webhooks with Ed25519. Each request includes telnyx-signature-ed25519

and telnyx-timestamp headers. Always verify signatures in production:

import com.telnyx.sdk.core.UnwrapWebhookParams;
import com.telnyx.sdk.core.http.Headers;

// In your webhook handler (e.g., Spring — use raw body):
@PostMapping("/webhooks")
public ResponseEntity<String> handleWebhook(
    @RequestBody String payload,
    HttpServletRequest request) {
  try {
    Headers headers = Headers.builder()
        .put("telnyx-signature-ed25519", request.getHeader("telnyx-signature-ed25519"))
        .put("telnyx-timestamp", request.getHeader("telnyx-timestamp"))
        .build();
    var event = client.webhooks().unwrap(
        UnwrapWebhookParams.builder()
            .body(payload)
            .headers(headers)
            .build());
    // Signature valid — process the event
    System.out.println("Received webhook event");
    return ResponseEntity.ok("OK");
  } catch (Exception e) {
    System.err.println("Webhook verification failed: " + e.getMessage());
    return ResponseEntity.badRequest().body("Invalid signature");
  }
}

Webhooks

These webhook payload fields are inline because they are part of the primary integration path.

Delivery Update

| Field | Type | Description |

|-------|------|-------------|

| data.event_type | enum: message.sent, message.finalized | The type of event being delivered. |

| data.payload.id | uuid | Identifies the type of resource. |

| data.payload.to | array[object] | |

| data.payload.text | string | Message body (i.e., content) as a non-empty string. |

| data.payload.sent_at | date-time | ISO 8601 formatted date indicating when the message was sent. |

| data.payload.completed_at | date-time | ISO 8601 formatted date indicating when the message was finalized. |

| data.payload.errors | array[object] | These errors may point at addressees when referring to unsuccessful/unconfirm... |

Inbound Message

| Field | Type | Description |

|-------|------|-------------|

| data.event_type | enum: message.received | The type of event being delivered. |

| data.payload.id | uuid | Identifies the type of resource. |

| data.payload.direction | enum: inbound | The direction of the message. |

| data.payload.to | array[object] | |

| data.payload.text | string | Message body (i.e., content) as a non-empty string. |

| data.payload.type | enum: SMS, MMS | The type of message. |

| data.payload.media | array[object] | |

| data.record_type | enum: event | Identifies the type of the resource. |

If you need webhook fields that are not listed inline here, read the webhook payload reference before writing the handler.

Important Supporting Operations

Use these when the core tasks above are close to your flow, but you need a common variation or follow-up step.

Send a group MMS message

Send one MMS payload to multiple recipients.

client.messages().sendGroupMms() — POST /messages/group_mms

|-----------|------|----------|-------------|

| to | array[object] | Yes | A list of destinations. |

| ... | | | +3 optional params in references/api-details.md |

import com.telnyx.sdk.models.messages.MessageSendGroupMmsParams;
import com.telnyx.sdk.models.messages.MessageSendGroupMmsResponse;

MessageSendGroupMmsParams params = MessageSendGroupMmsParams.builder()
    .from("+13125551234")
    .addTo("+18655551234")
    .addTo("+14155551234")
    .text("Hello from Telnyx!")
    .build();
MessageSendGroupMmsResponse response = client.messages().sendGroupMms(params);

Primary response fields:

response.data.id
response.data.to
response.data.from
response.data.type
response.data.direction
response.data.text

Send a long code message

Force a long-code sending path instead of the generic send endpoint.

client.messages().sendLongCode() — POST /messages/long_code

|-----------|------|----------|-------------|

| to | string (E.164) | Yes | Receiving address (+E.164 formatted phone number or short co... |

| ... | | | +6 optional params in references/api-details.md |

import com.telnyx.sdk.models.messages.MessageSendLongCodeParams;
import com.telnyx.sdk.models.messages.MessageSendLongCodeResponse;

MessageSendLongCodeParams params = MessageSendLongCodeParams.builder()
    .from("+18445550001")
    .to("+13125550002")
    .text("Hello from Telnyx!")
    .build();
MessageSendLongCodeResponse response = client.messages().sendLongCode(params);

Primary response fields:

response.data.id
response.data.to
response.data.from
response.data.type
response.data.direction
response.data.text

Send a message using number pool

Let a messaging profile or number pool choose the sender for you.

client.messages().sendNumberPool() — POST /messages/number_pool

|-----------|------|----------|-------------|

| to | string (E.164) | Yes | Receiving address (+E.164 formatted phone number or short co... |

| ... | | | +6 optional params in references/api-details.md |

import com.telnyx.sdk.models.messages.MessageSendNumberPoolParams;
import com.telnyx.sdk.models.messages.MessageSendNumberPoolResponse;

MessageSendNumberPoolParams params = MessageSendNumberPoolParams.builder()
    .messagingProfileId("abc85f64-5717-4562-b3fc-2c9600000000")
    .to("+13125550002")
    .text("Hello from Telnyx!")
    .build();
MessageSendNumberPoolResponse response = client.messages().sendNumberPool(params);

Primary response fields:

response.data.id
response.data.to
response.data.from
response.data.type
response.data.direction
response.data.text

Send a short code message

Force a short-code sending path when the sender must be a short code.

client.messages().sendShortCode() — POST /messages/short_code

|-----------|------|----------|-------------|

| to | string (E.164) | Yes | Receiving address (+E.164 formatted phone number or short co... |

| ... | | | +6 optional params in references/api-details.md |

import com.telnyx.sdk.models.messages.MessageSendShortCodeParams;
import com.telnyx.sdk.models.messages.MessageSendShortCodeResponse;

MessageSendShortCodeParams params = MessageSendShortCodeParams.builder()
    .from("+18445550001")
    .to("+18445550001")
    .text("Hello from Telnyx!")
    .build();
MessageSendShortCodeResponse response = client.messages().sendShortCode(params);

Primary response fields:

response.data.id
response.data.to
response.data.from
response.data.type
response.data.direction
response.data.text

Schedule a message

Queue a message for future delivery instead of sending immediately.

client.messages().schedule() — POST /messages/schedule

|-----------|------|----------|-------------|

| to | string (E.164) | Yes | Receiving address (+E.164 formatted phone number or short co... |

| ... | | | +8 optional params in references/api-details.md |

import com.telnyx.sdk.models.messages.MessageScheduleParams;
import com.telnyx.sdk.models.messages.MessageScheduleResponse;

MessageScheduleParams params = MessageScheduleParams.builder()
    .to("+18445550001")
    .from("+18005550101")

    .text("Appointment reminder")

    .sendAt("2025-07-01T15:00:00Z")
    .build();
MessageScheduleResponse response = client.messages().schedule(params);

Primary response fields:

response.data.id
response.data.to
response.data.from
response.data.type
response.data.direction
response.data.text

Send a WhatsApp message

Send WhatsApp traffic instead of SMS/MMS.

client.messages().sendWhatsapp() — POST /messages/whatsapp

|-----------|------|----------|-------------|

| to | string (E.164) | Yes | Phone number in +E.164 format |

import com.telnyx.sdk.models.messages.MessageSendWhatsappParams;
import com.telnyx.sdk.models.messages.MessageSendWhatsappResponse;
import com.telnyx.sdk.models.messages.WhatsappMessageContent;

MessageSendWhatsappParams params = MessageSendWhatsappParams.builder()
    .from("+13125551234")
    .to("+13125551234")
    .whatsappMessage(WhatsappMessageContent.builder().build())
    .build();
MessageSendWhatsappResponse response = client.messages().sendWhatsapp(params);

Primary response fields:

response.data.id
response.data.to
response.data.from
response.data.type
response.data.direction
response.data.body

Additional Operations

Use the core tasks above first. The operations below are indexed here with exact SDK methods and required params; use references/api-details.md for full optional params, response schemas, and lower-frequency webhook payloads.

Before using any operation below, read the optional-parameters section and the response-schemas section so you do not guess missing fields.

|-----------|------------|----------|----------|-----------------|

| Retrieve a message | client.messages().retrieve() | GET /messages/{id} | Fetch the current state before updating, deleting, or making control-flow decisions. | id |

| Cancel a scheduled message | client.messages().cancelScheduled() | DELETE /messages/{id} | Remove, detach, or clean up an existing resource. | id |

| Create an alphanumeric sender ID | client.alphanumericSenderIds().create() | POST /alphanumeric_sender_ids | Create or provision an additional resource when the core tasks do not cover this flow. | alphanumericSenderId, messagingProfileId |

| Retrieve an alphanumeric sender ID | client.alphanumericSenderIds().retrieve() | GET /alphanumeric_sender_ids/{id} | Fetch the current state before updating, deleting, or making control-flow decisions. | id |

| Delete an alphanumeric sender ID | client.alphanumericSenderIds().delete() | DELETE /alphanumeric_sender_ids/{id} | Remove, detach, or clean up an existing resource. | id |

| Retrieve group MMS messages | client.messages().retrieveGroupMessages() | GET /messages/group/{message_id} | Fetch the current state before updating, deleting, or making control-flow decisions. | messageId |

| Retrieve a messaging hosted number | client.messagingHostedNumbers().retrieve() | GET /messaging_hosted_numbers/{id} | Fetch the current state before updating, deleting, or making control-flow decisions. | id |

| Update a messaging hosted number | client.messagingHostedNumbers().update() | PATCH /messaging_hosted_numbers/{id} | Modify an existing resource without recreating it. | id |

| Regenerate messaging profile secret | client.messagingProfiles().actions().regenerateSecret() | POST /messaging_profiles/{id}/actions/regenerate_secret | Trigger a follow-up action in an existing workflow rather than creating a new top-level resource. | id |

| List alphanumeric sender IDs for a messaging profile | client.messagingProfiles().listAlphanumericSenderIds() | GET /messaging_profiles/{id}/alphanumeric_sender_ids | Fetch the current state before updating, deleting, or making control-flow decisions. | id |

| Get detailed messaging profile metrics | client.messagingProfiles().retrieveMetrics() | GET /messaging_profiles/{id}/metrics | Fetch the current state before updating, deleting, or making control-flow decisions. | id |

| List Auto-Response Settings | client.messagingProfiles().autorespConfigs().list() | GET /messaging_profiles/{profile_id}/autoresp_configs | Fetch the current state before updating, deleting, or making control-flow decisions. | profileId |

| Create auto-response setting | client.messagingProfiles().autorespConfigs().create() | POST /messaging_profiles/{profile_id}/autoresp_configs | Create or provision an additional resource when the core tasks do not cover this flow. | op, keywords, countryCode, profileId |

| Get Auto-Response Setting | client.messagingProfiles().autorespConfigs().retrieve() | GET /messaging_profiles/{profile_id}/autoresp_configs/{autoresp_cfg_id} | Fetch the current state before updating, deleting, or making control-flow decisions. | profileId, autorespCfgId |

| Update Auto-Response Setting | client.messagingProfiles().autorespConfigs().update() | PUT /messaging_profiles/{profile_id}/autoresp_configs/{autoresp_cfg_id} | Modify an existing resource without recreating it. | op, keywords, countryCode, profileId, +1 more |

| Delete Auto-Response Setting | client.messagingProfiles().autorespConfigs().delete() | DELETE /messaging_profiles/{profile_id}/autoresp_configs/{autoresp_cfg_id} | Remove, detach, or clean up an existing resource. | profileId, autorespCfgId |

Other Webhook Events

| Event | data.event_type | Description |

|-------|-------------------|-------------|

| replacedLinkClick | message.link_click | Replaced Link Click |

For exhaustive optional parameters, full response schemas, and complete webhook payloads, see references/api-details.md.

Other skills for the same job

different authors, same section of the catalogue

Meeting Insights Analyzer

by frostant

×8

Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.

Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".

53k tokens scripts

Developer Growth Analysis

by frostant

×6

Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.

Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack.

A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

2k tokens

Notion Meeting Intelligence

by openai

vendor ×2

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.

8k tokens scripts

How to use it

Copy the folder

Take team-telnyx/telnyx-messaging-java from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.