Skip to main content

Tyntec SMS

Availability
Available CoreAvailable StandardAvailable PlusAvailable ProAvailable Enterprise FlexAvailable PyAirbyte
Connector type (beta)
Available Data replicationNot available Agent(learn more)
Support Level
Marketplace
Connector Version
0.3.0 (last updated 7 days ago)
Data workers used
0.2 per sync (Learn more)
Definition ID
3c0c3cd1-b3e0-464a-9090-d3ceb5f92346

This page contains the setup guide and reference information for the Tyntec SMS source connector.

The connector uses the tyntec SMS API to send an SMS message you define in the connector configuration, then syncs the send result and the message's delivery status.

warning

This connector sends a real SMS message every time it runs. The connection check sends one message, and each selected stream sends its own message during a sync. A sync with both streams selected sends two messages. tyntec charges your account for each message.

Prerequisites​

  • A tyntec account with access to the tyntec Business Center.
  • A REST (web) gateway for SMS configured in the Business Center. tyntec requires a gateway before you can send SMS through the API. See tyntec's SMS quick start.
  • A tyntec API key.
  • A sender ID and a recipient phone number. During a tyntec trial, you can only send SMS to phone numbers you have verified (whitelisted) in the Business Center.

Setup guide​

Step 1: Get your tyntec API key​

  1. Log in to the tyntec Business Center.
  2. In the left navigation menu, click API Settings.
  3. Copy an existing API key, or create a new one.

tyntec issues separate API keys for trial and live environments. Use the key for the environment you want to send messages from.

Step 2: Set up the Tyntec SMS connector in Airbyte​

  1. In Airbyte, go to Sources and click New source.
  2. Select Tyntec SMS.
  3. Enter a name for the source.
  4. For Tyntec API Key, enter the API key from Step 1.
  5. For SMS Message Recipient Phone, enter the recipient's phone number in international format, for example +4915112345678.
  6. For SMS Message Sender Phone, enter the sender ID. This can be a phone number in international format or an alphanumeric sender ID of up to 11 characters. Some destination networks restrict which sender ID formats they accept.
  7. For SMS Message Body, enter the text of the message. Airbyte marks this field as optional, but tyntec's Send SMS endpoint requires a message, so enter a value.
  8. Click Set up source. Airbyte tests the connection by sending the configured message.

Supported sync modes​

The Tyntec SMS source connector supports the following sync modes:

FeatureSupported?
Full Refresh SyncYes
Incremental SyncNo

Supported streams​

StreamEndpointDescription
smsSend SMS (GET) GET /messaging/v1/smsSends the configured message and returns one record with the send result, including requestId, message parts, and prices.
messagesRead SMS status GET /messaging/v1/messages/{requestId}Sends the configured message, then reads that message's delivery status by its requestId.

Both streams use requestId as the primary key. The messages stream sends its own message rather than reusing the one from the sms stream, so the two streams return records with different requestId values.

Version 0.3.0 removed the contacts, phones, and registrations streams because tyntec no longer serves the BYON (Bring Your Own Number) endpoints they used. See the migration guide.

Limitations​

The connector can't read message history. It only returns data about the messages it sends during the current sync.

IP allow list​

If you use Airbyte Cloud and you enabled IP restriction on your tyntec account, add the Airbyte Cloud IP addresses to your tyntec IP allow list.

Reference​

Config fields reference

Field
Type
Property name
string
api_key
string
from
string
to
string
message

Changelog​

Expand to review
VersionDatePull RequestSubject
0.3.02026-10-0988337Remove the contacts, phones and registrations streams (tyntec BYON endpoints return 404) and use the sms stream for the connection check
0.2.252026-06-0279035Update dependencies
0.2.242025-05-2460738Update dependencies
0.2.232025-05-1059956Update dependencies
0.2.222025-05-0459537Update dependencies
0.2.212025-04-2758985Update dependencies
0.2.202025-04-1958045Update dependencies
0.2.192025-04-0557477Update dependencies
0.2.182025-03-2956294Update dependencies
0.2.172025-03-0855636Update dependencies
0.2.162025-03-0155151Update dependencies
0.2.152025-02-2254512Update dependencies
0.2.142025-02-1554061Update dependencies
0.2.132025-02-0853567Update dependencies
0.2.122025-02-0153063Update dependencies
0.2.112025-01-2552385Update dependencies
0.2.102025-01-1851961Update dependencies
0.2.92025-01-1151439Update dependencies
0.2.82024-12-2850783Update dependencies
0.2.72024-12-2150364Update dependencies
0.2.62024-12-1449793Update dependencies
0.2.52024-12-1249431Update dependencies
0.2.42024-12-1149110Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64
0.2.32024-11-0447910Update dependencies
0.2.22024-10-2843782Update dependencies
0.2.12024-08-1644196Bump source-declarative-manifest version
0.2.02024-08-1444054Refactor connector to manifest-only format
0.1.132024-08-1043551Update dependencies
0.1.122024-08-0343221Update dependencies
0.1.112024-07-2742689Update dependencies
0.1.102024-07-2042209Update dependencies
0.1.92024-07-1341740Update dependencies
0.1.82024-07-1041364Update dependencies
0.1.72024-07-0941108Update dependencies
0.1.62024-07-0640804Update dependencies
0.1.52024-06-2540482Update dependencies
0.1.42024-06-2239994Update dependencies
0.1.32024-06-0538838Make compatible with builder
0.1.22024-06-0439043[autopull] Upgrade base image to v1.2.1
0.1.12024-05-2138500[autopull] base image + poetry + up_to_date
0.1.02022-11-0218883🎉 New Source: Tyntec SMS
Was this page helpful?