canonical: https://jentic.com/apis/reviewnizer.com/reviewnizer

# Reviewnizer API

Reviewnizer API for managing review requests, SMS templates, timely messages, and customer engagement workflows. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get all sms templates, create sms template. Covers 8 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get All SMS Templates
- Create SMS Template
- Update SMS Template
- Delete SMS Template
- Monitor Reviewnizer API operational status and events

## Use cases

### Communications Operations

Use the Reviewnizer API to perform communications operations programmatically. The API provides 8 endpoints covering core functionality including get all sms templates, create sms template, get sms template.

Example prompt: Call POST `/reviewnizer/customer/timely-sms-template/table` to get all sms templates

### Automated `/Reviewnizer/Customer/TimelyMessages` Management

Automate `/reviewnizer/customer/timelymessages` operations by combining multiple Reviewnizer API endpoints. Agents can create sms template and then get sms template in a single workflow.

Example prompt: Call POST `/reviewnizer/customer/timely-sms-template`/ to create sms template, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Reviewnizer 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 apiKey tokens manually.

Example prompt: Search Jentic for 'get all sms templates', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/reviewnizer/customer/timely-sms-template/table` | Get All SMS Templates |
| POST | `/reviewnizer/customer/timely-sms-template/` | Create SMS Template |
| GET | `/reviewnizer/customer/timely-sms-template/{id}` | Get SMS Template |
| PUT | `/reviewnizer/customer/timely-sms-template/{id}` | Update SMS Template |
| DELETE | `/reviewnizer/customer/timely-sms-template/{id}` | Delete SMS Template |
| GET | `/reviewnizer/customer/timely-messages/get-contacts-list` | Get Contacts List |
| GET | `/reviewnizer/customer/timely-messages/get-templates-list` | Get Templates List |
| GET | `/status_codes/all` | Get All Status Codes |

## Key resources

- **`/Reviewnizer/Customer/TimelyMessages`** — Operations related to `/Reviewnizer/Customer/TimelyMessages`
- **`/Reviewnizer/Customer/TimelySmsTemplate`** — Operations related to `/Reviewnizer/Customer/TimelySmsTemplate`
- **Status Codes** — Operations related to Status Codes

## Why Jentic

- **Setup:** Wiring the Reviewnizer API by hand means handling its token header auth, sending that token on every call to api.reviewnizer.com, and managing retries yourself. Through Jentic you install once, import the Reviewnizer API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Reviewnizer puts the template id in the URL path (`/reviewnizer/customer/timely-sms-template/{id}`), so a rule can pin your agent to one SMS template: it can read that template and nothing else. You choose the operations it may call, so destructive ones like deleting or updating a template are not included unless you add them.
- **Credential handling:** Your Reviewnizer 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 'get all SMS templates' or 'list contacts', and Jentic returns the matching Reviewnizer API 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 Reviewnizer API use?

The Reviewnizer API uses an API key passed in the `token` 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 get all sms templates with the Reviewnizer API?

Yes. Use the POST `/reviewnizer/customer/timely-sms-template/table` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Reviewnizer 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 get all sms templates through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get all sms templates'. Jentic returns the matching Reviewnizer API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Reviewnizer API have?

The Reviewnizer API exposes 8 endpoints covering `/reviewnizer/customer/timelymessages`, `/reviewnizer/customer/timelysmstemplate`, status codes operations.

### Can I limit what my agent is allowed to do with the Reviewnizer API?

Yes. Because you run Jentic One yourself, your own rules decide which Reviewnizer operations and credentials the agent may use. Reviewnizer puts the template id in the URL path (`/reviewnizer/customer/timely-sms-template/{id}`), so you can pin the agent to a single SMS template and let it only read that template. You also choose the operations it may call, so destructive ones like deleting or updating a template stay off unless you explicitly add them.