Component
core/messaging/telnyx
A messaging and voice carrier reached over Telnyx's REST API, so an application sends a text message or places a call without operating telephony infrastructure. The developer names the modality, text or call, and the direction, outbound, inbound or both; the operator supplies the API base address. Wire here rather than to a broker: a broker delivers inside the Release, a carrier onto the public networks. Consumers read the base address, the modality and the direction. Realized by reference: no compute runs here.
Provenance
- Content digest
- sha256:95643bd8c14581024a0b949bcda3150d3d51b0d6d6360d895b52016e4bf2d38a
- Published
- 2026-11-10T10:12:35Z
- Signing identity
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signature
- Officialapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:27e2ef0c63654b6724838fca365b317282bcae536af04654526663fe14f25c7d
Reference at this version
oci://hub.aggrega.ai/component/core/messaging/telnyx:1.0.0Developer parameters
Values the developer sets in the Aggregate.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| modality | string (sms | voice) | sms | no | Which of the carrier's two channels this wiring addresses — a text message, or a call. |
| direction | string (outbound | inbound | bidirectional) | outbound | no | Whether the application originates traffic, receives it, or both. |
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| endpoint | string | https://api.telnyx.com | no | — |
Output contract
Values this component publishes to consumers over the uses topology.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| endpoint | string | — | yes | Base URL of the carrier's API an application calls to send a message or place a call. The Release supplies it, so an operator may point it at a different host without the application changing. |
| modality | string | — | yes | Which of the carrier's two channels this wiring addresses — a text message, or a call — carried through from the value the Aggregate declared. A consumer reads it to pick the request shape it sends. |
| direction | string | — | yes | Whether the application originates traffic on this wiring, receives it, or both, carried through from the value the Aggregate declared. A consumer reads it to know whether it must also stand up a receiving path. |
Uses sockets
The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.
No uses sockets declared.
Attachment slots
Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.
| Slot | Selector | Required | Inject | Sensitive | Description |
|---|---|---|---|---|---|
| api_key | feature.aggrega.ai/kind=secret | no | env | yes | The bearer token carried in the authorization header of every request to the carrier. |
Self-inject allowlist
No self-inject pipes declared.
Relationships
Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.
Uses
This entity uses nothing in the catalog.
Used by
implements
implements