canonical: https://jentic.com/apis/remindlo.co.uk/remindlo

# Remindlo SMS Reminder API

SMS reminder and campaign management API for automated customer communications. The API exposes 6 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list campaigns, create or update contact. Covers 6 operations with apiKey authentication.

## Scope

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

## Capabilities

- List campaigns
- Create or update contact
- Get contact
- Enroll in campaign
- Send SMS message

## Use cases

### Marketing Operations

Use the Remindlo SMS Reminder API to perform marketing operations programmatically. The API provides 6 endpoints covering core functionality including list campaigns, create or update contact, list contacts.

Example prompt: Call GET /campaigns to list campaigns

### Automated Campaigns Management

Automate campaigns operations by combining multiple Remindlo SMS Reminder API endpoints. Agents can create or update contact and then list contacts in a single workflow.

Example prompt: Call POST /contacts to create or update contact, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Remindlo SMS Reminder 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 'list campaigns', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/campaigns` | List campaigns |
| POST | `/contacts` | Create or update contact |
| GET | `/contacts` | List contacts |
| GET | `/contacts/{id}` | Get contact |
| POST | `/campaigns-enroll` | Enroll in campaign |
| POST | `/messages` | Send SMS message |

## Key resources

- **Campaigns** — Operations related to Campaigns
- **Contacts** — Operations related to Contacts
- **Messages** — Operations related to Messages

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 85 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/remindlo.co.uk/remindlo/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Remindlo by hand means sending its sk_live x-api-key header to api.remindlo.co.uk and mapping its campaign, contact, and message endpoints yourself. Through Jentic you install once, import Remindlo from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Remindlo puts the contact id in the URL path (`/contacts/{id}`), so a rule can pin your agent to reading one contact and listing campaigns. You choose the operations it may call, so sending messages or enrolling contacts in campaigns is not included unless you add them.
- **Credential handling:** Your Remindlo API key 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 'list campaigns' or 'look up a contact', and Jentic returns the matching Remindlo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the Remindlo SMS Reminder API use?

The Remindlo SMS Reminder API uses an API key passed in the `x-api-key` 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 list campaigns with the Remindlo SMS Reminder API?

Yes. Use the GET /campaigns endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Remindlo SMS Reminder 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 list campaigns through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list campaigns'. Jentic returns the matching Remindlo SMS Reminder API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Remindlo SMS Reminder API have?

The Remindlo SMS Reminder API exposes 6 endpoints covering campaigns, contacts, messages operations.

### Can I limit what my agent is allowed to do with the Remindlo SMS Reminder API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Remindlo operations and credentials the agent may use. Because Remindlo puts the contact id in the URL path (`/contacts/{id}`), you can pin the agent to read a single contact and list campaigns while withholding write operations. Sending SMS messages (POST /messages) or enrolling contacts in campaigns (POST /campaigns-enroll) stays off limits unless you explicitly add those operations.