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

# Riserphone Riser Zapier API

Riser phone system API for contact management. Supports contact CRUD and polling triggers. The API exposes 5 endpoints secured with apiKey authentication.

## For AI agents

Programmatically validate account and API key, list newest contacts. Covers 5 operations with apiKey authentication.

## Scope

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

## Capabilities

- Validate account and API key
- List newest contacts
- Create or upsert a contact
- Query and filter Riser Zapier API records by parameters
- Monitor Riser Zapier API operational status and events

## Use cases

### CRM Operations

Use the Riser Zapier API to perform crm operations programmatically. The API provides 5 endpoints covering core functionality including validate account and API key, list newest contacts, list recently updated contacts.

Example prompt: Call GET `/api/zapier/validate-account-access` to validate account and API key

### Automated Auth Management

Automate auth operations by combining multiple Riser Zapier API endpoints. Agents can list newest contacts and then list recently updated contacts in a single workflow.

Example prompt: Call GET `/api/zapier/new_contacts` to list newest contacts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Riser Zapier 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 'validate account and API key', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/zapier/validate-account-access` | Validate account and API key |
| GET | `/api/zapier/new_contacts` | List newest contacts |
| GET | `/api/zapier/updated_contacts` | List recently updated contacts |
| GET | `/api/zapier/deleted_contacts` | List deleted contacts |
| POST | `/api/zapier/create_contact` | Create or upsert a contact |

## Key resources

- **Auth** — Operations related to Auth
- **Contacts** — Operations related to Contacts
- **Webhooks** — Operations related to Webhooks

## 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:** 47 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/riserphone.com/riserphone/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 the Riser Zapier API by hand means registering an api_key, appending it as a query parameter on every call to the riserphone.com host, and validating account access before syncing contacts yourself. Through Jentic you install once, import the Riser Zapier API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API takes the contact details in the request body rather than a resource id in the path, so scope the agent to the operations it needs, such as reading new or updated contacts: you can grant those reads without allowing create_contact. Every operation the agent can run is one you have added to that allowed set.
- **Credential handling:** Your Riser 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 new contacts' or 'create a contact', and Jentic returns the matching Riser Zapier API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Riser Zapier API use?

The Riser Zapier API uses an API key passed in the `api_key` query. 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 validate account and API key with the Riser Zapier API?

Yes. Use the GET `/api/zapier/validate-account-access` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Riser Zapier 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 validate account and API key through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validate account and API key'. Jentic returns the matching Riser Zapier API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Riser Zapier API have?

The Riser Zapier API exposes 5 endpoints covering auth, contacts, webhooks operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Riser Zapier API operations and credentials the agent may use. You can grant read-only access to endpoints like GET `/api/zapier/new_contacts`, `/api/zapier/updated_contacts`, and `/api/zapier/deleted_contacts` while withholding POST `/api/zapier/create_contact`, so the agent lists and monitors contacts without writing new ones. Every operation the agent can call is one you have added to that allowed set.