Docs
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Open dashboard
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Getting started
  • Overview
  • Start guide
  • Project status
  • Concepts
AI
  • Iris
  • AI writing
  • Connect your AI (MCP)
Channels
    • Countries & coverage
    • Senders & registration
    • Essentials
    • Countries & availability
    • What is RCS
    • Senders & verification
    • Agent profile
    • Best practices
    • Acceptable use
    • SMS fallback
  • WhatsAppSoon
  • Compliance
  • Countries
    • Austria
    • Brazil
    • Canada
    • Colombia
    • France
    • Germany
    • India
    • Indonesia
    • Mexico
    • Netherlands
    • Peru
    • Singapore
    • Spain
      • Authorise the alias
      • Register directly
      • Without a certificate
      • Rejected alias
    • Ukraine
    • United Kingdom
    • United States
    • Other countries
Marketing
  • Campaigns
    • Creating a campaign
    • Targeting
    • Test sends
    • Delivery
    • Compliance
    • Managing campaigns
    • Campaign analytics
  • Flows
    • Building a flow
    • Templates
    • Triggers & entry
    • Sending messages
    • Waits
    • Branches
    • Contact updates
    • Goals & exits
    • Versions & publishing
    • Managing flows
    • Monitoring
    • Analytics
    • Limits
  • Sequences (legacy)
    • Managing sequences
    • Sequence analytics
Data
  • Audience
    • Contacts
    • Audience table
    • Segments
    • Attributes & events
  • Integrations & data sources
    • Managing sources
    • CSV import
    • API & webhooks
    • Integrations
      • Shopify
      • Klaviyo
      • WooCommerce
      • PrestaShop
      • Magento
      • HighLevel
      • Hotmart
      • ActiveCampaign
      • Zoom
      • Facebook Leads
      • Google Sheets
      • Google Contacts
      • MailChimp
      • MailerLite
      • Intercom
      • Make
      • Zapier
      • Activepieces
      • n8n
      • Pabbly Connect
      • OptiMonk
      • Paperform
      • StockAgile
      • Typeform
  • Consent
    • How consent works
    • Subscription attributes
    • Shared consent
    • Opt-outs
    • Manage via API
Analytics
  • Audience
  • Messages
  • Sales
  • Reports
Settings
  • Project settings
    • Brand profile
    • Senders
    • Short links
    • Unsubscribe links
    • Test numbers
    • Attribution
    • Project memory
  • Developers & Apps
    • API tokens
    • Third-party apps
    • Data access
    • Connected apps
  • Organization
    • General
    • Legal profiles
    • Team
    • Localization
  • Billing
    • Plans
    • Cost calculator
    • Balance
    • Invoices
    • Pricing
    • Account
    • Theme
    • Security
    • Notifications
    • Language & currency
DashboardSupportinstasent.com

Settings

Developers & Apps

Everything that reaches your Instasent project from outside: your own code with an API token, the AI assistant you already use, and third-party apps connected over OAuth — each with permissions you approve and can revoke.

On this page▾
  • Which one is your case
  • What none of them do
  • Two things this is not

Your Instasent project doesn't only get worked on from the dashboard. Your own software can read and write to it, the AI assistant you already use can explore it and prepare work for you, and tools like Zapier or your CRM can operate it on your behalf. This section covers all three, and they are more alike than they look: each one gets the access you approve, reaches only the projects you pick, and can be cut off whenever you want.

Where they differ is who holds the credential and who hands it out — and that single question decides which of the three you need.

Which one is your case

Your own code

You are writing the integration yourself and your server will call Instasent. You create an API token, scope it, and your code carries it. Nobody else is involved.

Your AI

You want Claude, ChatGPT or the assistant you already work in to read your audience, campaigns and reports and prepare work with you. You connect it once and it uses your model.

A third-party app

Software somebody else built — an automation platform, a CRM — that operates your project for you. You authorize it, and it never sees your password.

The last two go through the same door: an authorization screen where you sign in, choose the project and see exactly what is being asked for. Both then appear together in Connected apps, which is where you check what each one reaches and disconnect the ones you no longer want.

What they can see

The access type you set per project, and how much of your audience data actually leaves it.

Managing what's connected

Review every connection, change which projects it reaches, and disconnect it.

What none of them do

Nothing connected here sends a message, launches a campaign or starts an automation on its own. They read, they prepare, and they leave the work ready for you — you press send in the dashboard. That is a design decision, not a limitation of the current version.

Two things this is not

  • It is not the AI built into Instasent. Iris and the writing help live inside the dashboard and there is nothing to connect: see Integrated AI. Bringing your own assistant is Connect your AI.
  • It is not how data gets into Instasent. Shopify, CSV imports, webhooks and the rest of the connectors feed your audience, and they live in Data sources. The arrow points the other way: data sources bring data in, and what's on this page operates the project from outside.

Last updated October 8, 2026

PreviousIrisNextAPI tokens
  • Which one is your case
  • What none of them do
  • Two things this is not

© 2026 Instasent

Privacy PolicyTerms & ConditionsCookie PolicyLegal Notice
All systems operational