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

# Re:amaze API

Re:amaze customer support platform API for managing conversations, contacts, articles, channels, reports, and more. The API exposes 38 endpoints secured with basic authentication.

## For AI agents

Programmatically create article, list articles. Covers 38 operations with basic authentication.

## Scope

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

## Capabilities

- Create article
- List articles
- Get article
- Update article
- Access Re:amaze API crm resources via REST API

## Use cases

### CRM Operations

Use the Re:amaze API to perform crm operations programmatically. The API provides 38 endpoints covering core functionality including create article, list articles, get article.

Example prompt: Call POST /articles to create article

### Automated Articles Management

Automate articles operations by combining multiple Re:amaze API endpoints. Agents can list articles and then get article in a single workflow.

Example prompt: Call GET /articles to list articles, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Re:amaze 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 basic tokens manually.

Example prompt: Search Jentic for 'create article', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/articles` | Create article |
| GET | `/articles` | List articles |
| GET | `/articles/{id}` | Get article |
| PUT | `/articles/{id}` | Update article |
| GET | `/channels` | List channels |
| GET | `/channels/{id}` | Get channel |
| POST | `/contacts` | Create contact |
| GET | `/contacts` | List contacts |

## Key resources

- **Articles** — Operations related to Articles
- **Channels** — Operations related to Channels
- **Contacts** — Operations related to Contacts
- **Conversations** — Operations related to Conversations
- **Messages** — Operations related to Messages

## Why Jentic

- **Setup:** Wiring the Re:amaze API by hand means encoding your key as HTTP basic auth, substituting your brand subdomain into the host, and managing articles, channels, and contacts with paging and retries yourself. Through Jentic you install once, import the Re:amaze API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The Re:amaze API puts the resource id in the URL path (`/articles/{id}`) under your brand subdomain, so a rule can pin your agent to one article. You choose the operations it may call, so it can read and update that article while other operations stay out of scope unless you add them.
- **Credential handling:** Your Re:amaze API basic credential 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 'create an article' or 'list contacts', and Jentic returns the matching Re:amaze 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 Re:amaze API use?

The Re:amaze API uses HTTP Basic authentication. 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 create article with the Re:amaze API?

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

### What are the rate limits for the Re:amaze 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 create article through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create article'. Jentic returns the matching Re:amaze API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Re:amaze API have?

The Re:amaze API exposes 38 endpoints covering articles, channels, contacts operations.

### Can I limit what my agent is allowed to do with the Re:amaze API?

Yes. Because Jentic One is self-hosted, your own rules decide which Re:amaze API operations and credentials the agent may use. Since the resource id sits in the URL path (`/articles/{id}`) under your brand subdomain, you can pin the agent to a single article and grant only the operations you choose, such as GET `/articles/{id}` to read it and PUT `/articles/{id}` to update it. Other operations, like creating contacts or listing channels, stay out of scope until you add them.