canonical: https://jentic.com/apis/remo.co/remo # Remo API Remo Conference API for managing virtual events and registrations. The API exposes 1 endpoints secured with apiKey authentication. ## For AI agents Programmatically notify user when there are new registrations. Covers 1 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - Notify user when there are new registrations - Manage developer tools data programmatically - Integrate Remo API into automated workflows - Query and filter Remo API records by parameters - Monitor Remo API operational status and events ## Use cases ### Developer Tools Operations Use the Remo API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including notify user when there are new registrations. Example prompt: Call GET `/api/v1/zapier/new-event-users` to notify user when there are new registrations ### Data Retrieval and Monitoring Query Remo API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed. Example prompt: Poll the primary Remo API endpoint, compare response to last known state, and alert if changed ### AI Agent Integration via Jentic AI agents discover and call Remo 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 'notify user when there are new registrations', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/zapier/new-event-users` | Notify user when there are new registrations | ## Key resources - **admins** — Secured Admin-only calls - **developers** — Operations available to regular developers ## 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:** 57 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 51 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 25 / 100 - **View full report:** https://jentic.com/apis/remo.co/remo/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 ``` ## Why Jentic - **Setup:** Wiring Remo by hand means sending its Authorization header and polling its single new-event-users endpoint yourself. Through Jentic you install once, import Remo from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Remo exposes one read endpoint for new event users, so limit the agent to that operation. You choose the operations it may call, so nothing beyond reading new registrations runs unless you add it. - **Credential handling:** Your Remo 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 'notify when there are new registrations', and Jentic returns the matching Remo operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Github** — Alternative developer tools API - **Gitlab** — Alternative developer tools API ## FAQ ### What authentication does the Remo API use? The Remo API uses an API key passed 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 notify user when there are new registrations with the Remo API? Yes. Use the GET `/api/v1/zapier/new-event-users` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Remo 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 notify user when there are new registrations through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'notify user when there are new registrations'. Jentic returns the matching Remo API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Remo API have? The Remo API exposes 1 endpoints covering admins, developers operations. ### Can I limit what my agent is allowed to do with the Remo API? Yes. Because Jentic One is self-hosted, you define the rules that decide which Remo operations and credentials your agent may use. The Remo API exposes a single read endpoint, GET `/api/v1/zapier/new-event-users` for new event registrations, so you can restrict the agent to just that call and nothing else runs unless you explicitly add it. Your Remo API key stays with your own instance and is injected only when an allowed operation executes.