Docs
Sign up

Introduction

Instasent is a customer messaging platform with four public APIs. This introduction is the map — what each API does, how they fit together, and where to start.

Instasent powers customer messaging — SMS today, more channels to come. The platform exposes four public HTTP APIs, plus SMPP for high-volume SMS and SDKs for the most common languages. Whether you are managing audiences, ingesting customer data, or sending transactional messages, there is an API scoped to that job.

This page is a map. When you know what you need, jump straight into the API guide. When you don't, start with Choose your API.

The four APIs

Product API

Control plane of the platform — organizations, projects, audiences, datasources. Also sends transactional messages registered against project contacts.

Ingest API

High-volume ingestion of contacts and events. A subset of Product scoped to a single datasource.

Transactional API

Direct messaging over HTTP or SMPP. SDKs available in Node.js, PHP, Python, Ruby and Java. Also known as the SMS API.

Legacy API

The original root API, kept alive for existing integrations. Not recommended for new work.

How the APIs relate

The Product API sits above everything else: it manages the entities (organizations, projects, audiences) that the other APIs operate on, and it can also send messages registered against project contacts — useful when you want delivery tracked alongside customer history. The Ingest API is a surface-narrowed subset of Product, optimised for throughput when you only need to push contacts and events. The Transactional API is independent and focused on the raw act of sending a message, without touching project data — the right choice when you don't need the message recorded against a contact.