Revolt API

Name: Revolt API API
Brand: Revolt API
Availability: InStock

✓ Official Vendor SpecCommunicationsSms MessagingapiKey16 EndpointsREST

For Agents

Programmatically get current user, edit current user. Covers 16 operations with apiKey authentication.

Use for: I need to current user, I want to edit current user, Search for user, Find all channel

Connect the Revolt API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Revolt API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Revolt API API.

Get current user

Edit current user

Close/delete channel

Send message

Monitor Revolt API operational status and events

GET STARTED

Start building with Revolt API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Revolt API API for, with concrete tasks.

★ Communications Operations

Use the Revolt API to perform communications operations programmatically. The API provides 16 endpoints covering core functionality including get current user, edit current user, get user.

Call GET /users/@me to get current user

Automated Users Management

Automate users operations by combining multiple Revolt API endpoints. Agents can edit current user and then get user in a single workflow.

Call PATCH /users/@me to edit current user, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Revolt 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.

Search Jentic for 'get current user', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

16 endpoints — api for revolt, an open source discord alternative.

METHOD

PATH

DESCRIPTION

GET

/users/@me

Get current user

PATCH

/users/@me

Edit current user

GET

/users/{userId}

Get user

GET

/channels/{channelId}

Get channel

PATCH

/channels/{channelId}

Edit channel

DELETE

/channels/{channelId}

Close/delete channel

POST

/channels/{channelId}/messages

Send message

GET

/channels/{channelId}/messages

Get messages

GET

/users/@me

Get current user

PATCH

/users/@me

Edit current user

GET

/users/{userId}

Get user

GET

/channels/{channelId}

Get channel

PATCH

/channels/{channelId}

Edit channel

DELETE

/channels/{channelId}

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Revolt API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get current user') and Jentic returns the matching Revolt API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Revolt API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio

Alternative communications API

Choose Twilio when you need a different approach to communications operations

Alternative

Sendgrid

Alternative communications API

Choose Sendgrid when you need a different approach to communications operations

Complementary

Pusher

Complementary communications API

Choose Pusher when you need a complementary approach to communications operations

FAQs

Specific to using Revolt API API through Jentic.

What authentication does the Revolt API use?

The Revolt API uses an API key passed in the `x-session-token` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I get current user with the Revolt API?

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

What are the rate limits for the Revolt 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 current user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get current user'. Jentic returns the matching Revolt API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Revolt API have?

The Revolt API exposes 16 endpoints covering users, channels, messages operations.