Docs / Data sources / tyntec SMS

tyntec SMS

Business software

Built when you ask for it

Sync tyntec SMS message, conversion, and number data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The tyntec SMS connector syncs your messaging API data into analytics-ready tables in your data warehouse. Pull messages, conversions, and numbers from the tyntec API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Messages
  • Conversions
  • Numbers

How it gets built

  1. Choose tyntec SMS when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads tyntec SMS's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against tyntec SMS itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API key (apikey header). No public self-serve signup: contact tyntec for an API key.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a tyntec SMS connector?
Not as a finished connector yet. Ingest builds it from tyntec SMS's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can tyntec SMS data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

tyntec SMS API documentation: https://api.tyntec.com/reference/sms/current.html

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request tyntec SMS