canonical: https://jentic.com/apis/swaggerhub.advancedcomputersoft/advanced-notification-platform-integration-api

# Advancedcomputersoft Advanced Notification Platform Integration API

Advanced Notification Platform Integration API provides API for products to send notification content for delivery of the notification via InApp, Push, SMS or Email. The API also allows products to check for Notification delivery status and Notification history. The API exposes 19 endpoints secured with bearer authentication.

## For AI agents

Programmatically token generation, create a new rule. Covers 19 operations with bearer authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Token generation
- Create a new rule
- List product rules
- Get rule by code
- Update product rule
- Delete product rule
- Send notification

## Use cases

### Communications Operations

Use the Advanced Notification Platform Integration API to perform communications operations programmatically. The API provides 19 endpoints covering core functionality including token generation, create a new rule, list product rules.

Example prompt: Call POST /authorization/token-generation to token generation

### Automated Authorization Management

Automate authorization operations by combining multiple Advanced Notification Platform Integration API endpoints. Agents can create a new rule and then list product rules in a single workflow.

Example prompt: Call POST /rules to create a new rule, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Advanced Notification Platform Integration API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'token generation', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /authorization/token-generation | Token generation |
| POST | /rules | Create a new rule |
| GET | /rules | List product rules |
| GET | /rules/{ruleCode} | Get rule by code |
| PUT | /rules/{ruleCode} | Update product rule |
| DELETE | /rules/{ruleCode} | Delete product rule |
| POST | /notifications | Send notification |
| GET | /notification-logs | Notification log by job Id |

## Key resources

- **Authorization** — Token generation operation
- **Notification** — Operations to send notification and retrieve notification status
- **Rules** — Operations to maintain product rules
- **GeneralConfiguration** — Operations to maintain general configuration
- **SMS Configuration** — Operations to maintain sms configurations

## Why Jentic

- **Setup:** Wiring the Advanced Notification Platform Integration API by hand means calling /authorization/token-generation for a bearer token, choosing between the api.oneadvanced.io host and the AWS execute-api host, and managing rules and notification sends yourself. Through Jentic you install once, import the Advanced Notification Platform Integration API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** The Notification Platform API puts the rule code in the URL path (/rules/{ruleCode}), so a rule can pin your agent to one notification rule for reads and updates. You choose the operations it may call, so destructive ones like deleting a rule are not included unless you add them.
- **Credential handling:** Your Advanced Notification Platform bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'generate an access token' or 'send a notification', and Jentic returns the matching Advanced Notification Platform operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Advanced Notification Platform Integration API use?

The Advanced Notification Platform Integration API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I token generation with the Advanced Notification Platform Integration API?

Yes. Use the POST /authorization/token-generation endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Advanced Notification Platform Integration API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I token generation through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'token generation'. Jentic returns the matching Advanced Notification Platform Integration API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Advanced Notification Platform Integration API have?

The Advanced Notification Platform Integration API exposes 19 endpoints covering authorization, notification, rules operations.

### Can I limit what my agent is allowed to do with the Advanced Notification Platform Integration API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call and which bearer credentials it uses, so you can grant sending notifications through POST /notifications while withholding destructive operations like DELETE /rules/{ruleCode}. Since the rule code sits in the URL path, you can pin the agent to reading or updating a single notification rule rather than every product rule. Only the operations you explicitly allow are exposed to the agent.