Platform Overview Sense Decide Act Learn Allyvate AI Inform Security & Compliance Integrations
Banking & Finance Telecommunications Healthcare Insurance Wealth Management Government
Case Studies By Role Documentation Read More Switch to Appice Value Management
Partners Overview Technology Partners Implementation Partners Management Consultants
Book a Demo
Home/Documentation/APIs and ANS

APIs and ANS

Use Appice APIs and ANS to support backend-driven notifications, callback webhooks, and enterprise integrations.

Appice InformANS · Agentic Notification System

What Appice Inform ANS is

The Agentic Notification System (ANS) is a backend-driven notification architecture described in the manual. It allows internal systems to send transactional or marketing notifications through Appice without relying on direct exposure of personal data in every operational step.

It is particularly useful when enterprise systems need a privacy-preserving bridge to user devices, channels, or campaign execution logic.

Campaign automation workflow

The manual describes two main flows:

  1. Internal-system initiated flow where backend systems send notification parameters through ANS to Appice.
  2. Panel-created campaign flow where business users create the campaign in Appice, then use the generated campaign ID inside the internal system.
This is one of Appice’s stronger enterprise patterns. It deserves a polished explainer diagram in the production version of the site.

sendCampaignByID

The key API described in the manual is sendCampaignByID, which sends a campaign to a list of users, emails, MSISDNs, tokens, or a segment, depending on what identifiers are provided.

POST /i/V1/sendCampaignByID Content-Type: application/json { "app_id": "your_app_id", "app_key": "your_app_key", "api_key": "your_api_key", "camp_data": { "id": "campaign-id", "name": "push-template-name", "users": ["user-1", "user-2"], "payload": [{ "ctype": "PUSH", "dtype": "InboxOnly", "nh": "Header text", "nd": "Description text", "lang": "en-us", "expiry": "2026-12-31T23:59:59", "cdata": {"title": "Successful Payment", "body": "Successful Payment"} }] } }

In a later version of the help center, this should be split into dedicated endpoint pages with request tables, field descriptions, and sample responses.

Webhooks

Webhooks are used both for outbound gateway-triggering patterns and for inbound callback patterns. For example, an SMS provider may need Appice to call an external endpoint, while an email or messaging gateway may call back into Appice with delivery or engagement events.

Architecture and hosting note

The manual includes deployment and architecture material for on-premise-style enterprise setups, including storage, databases, load balancing, orchestration, and certificates. For the help center, keep infrastructure content in a separate technical section so it does not overwhelm business users looking for campaign guidance.