Reference · built on requestConnectorSupport & service desks

Re:amaze

Conversations, messages, contacts, channels, and satisfaction ratings from a Re:amaze brand through its REST API.

Request accessPricing ↗

About

Re:amaze is a help desk and chat platform organized by brand. Each brand serves its own API at https://{brand}.reamaze.io/api/v1/ and exposes conversations, messages, contacts, contact notes, channels, staff, response templates, articles, and satisfaction ratings. Conversations carry a numeric status, a category that maps to a channel, tags, an assignee, and a custom data hash.

Through Fibric, an operator polls the conversation list, reads the last customer message and the contact, and proposes a reply, an internal note, an assignment, or a status change for your approval. Each approved write is sent with an origin_id so a retry cannot post the same message twice.

This is a reference listing. It documents what Fibric would read from Re:amaze and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Conversations through GET /conversations, filtered by open, unassigned, archived, or all, and sorted by updated or changed
  • Conversation status as an integer: Open, Responded, Done, Spam, Archived, On Hold, Auto-Done, and the AI Agent states
  • Messages on a conversation, with body, visibility, and author
  • Contacts, contact identities, and contact notes
  • Channels, staff, and response templates
  • Satisfaction ratings and the Volume, Response Time, Staff, Tags, and Channel Summary reports
  • Status page incidents and systems

Proposed actions

  • Target capability: propose a reply through POST /conversations/{slug}/messages with visibility 0
  • Target capability: propose an internal note through the same endpoint with visibility set to 1
  • Target capability: propose an assignee, tag_list, or status change through PUT /conversations/{slug}, including hold_until for On Hold
  • Target capability: propose a contact note through the Contact Notes resource

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Draft the first reply while the conversation is still open

    The operator reads new conversations with filter set to open, matches the closest response template, and proposes a reply for approval with suppress_autoresolve left off.

    With First Response, Macro Match

  • Answer a where-is-my-order chat from the store record

    For a shipping question, the operator looks up the contact's order in your commerce platform and proposes a reply with the tracking status.

    With WISMO Deflection

  • Clear conversations that customers have stopped answering

    The operator lists conversations sorted by changed, finds those with no customer message since the last staff reply, and proposes a status change to Done in one batch.

    With Backlog Sweep

Requirements

  • A Re:amaze account and the brand host that forms the base URL https://{brand}.reamaze.io/api/v1/
  • A staff user whose API token the connector will use; every user gets an individual token
  • Requests that send Accept: application/json or use the .json suffix
Authentication
HTTP Basic authentication over HTTPS, using a staff login email and the per-user API token generated under Settings, Developer, API Token.

Limits

  • Requests are rate limited per minute per API token; the count is not published, and excess calls return HTTP 429
  • The API page documents no webhooks, so conversation changes are read by polling GET /conversations with sort set to changed
  • Moving a conversation with the category field works for email channels only
  • Responses are JSON only; JSONP is not offered

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Re:amaze ↗

Questions and answers

How does Re:amaze authenticate API calls?
With HTTP Basic authentication over HTTPS. The username is a staff login email and the password is that user's API token, generated under Settings, Developer, API Token. Each user has an individual token.
Can the connector post a note that the customer does not see?
Yes. POST /conversations/{slug}/messages takes a visibility field. The value 0 is a regular message and 1 is an internal note. The request can also carry suppress_notifications, suppress_autoresolve, and suppress_surveys.
How are conversation changes detected without webhooks?
By polling GET /conversations. The sort parameter accepts updated, which orders by the last customer message, or changed, which orders by any update or status change. Responses include page_size, page_count, and total_count for paging.
Ask about Re:amaze

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Re:amaze through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy