Skip to content
ReplycoReplycoAPI

Support and feature requests

These two operations let your integration reach Replyco itself rather than your customers: open a ticket with the Replyco support team, or suggest a feature on the public Comrce roadmap. Both act for the user your access token was issued for.

Support tickets

Section titled “Support tickets”

POST /openapi/support/create-ticket opens a ticket with the Replyco support team. It is filed under your user’s email address, and support replies to that address by email. Your user and company details are attached for the support team, so you do not need to repeat them in the text.

Field Rules
subject Required; up to 200 characters after surrounding spaces are removed.
text Required; plain text, up to 10,000 characters. Line breaks are kept; HTML is shown as text. 
{
  "subject": "Orders from our shop are missing customer names",
  "text": "Since 20 October, orders we create through the API show no customer name in Replyco.\nExample order: EX-100245."
}
{
  "id": "2718281828"
}

Quote the id when you contact support about the issue.

Feature requests

Section titled “Feature requests”

POST /openapi/support/feature-requests posts a feature request to the public Comrce roadmap, in the Replyco category. The post is published without your name or email address; the support team is told separately who asked.

Field Rules
title Required; plain text, up to 200 characters.
description Optional; plain text or Markdown, not HTML, up to 10,000 characters. 
{
  "title": "Filter tickets by order status",
  "description": "We would like to list tickets whose order is **not yet shipped**."
}
{
  "id": "31415",
  "url": "https://roadmap.example.com/p/31415",
  "supportTicketId": "2718281829"
}

The response gives the roadmap post’s id and url (empty when no public link is available), and in supportTicketId the support ticket that records who asked. supportTicketId can be empty while the feature request itself was created: do not send the request again.

Failures and retries

Section titled “Failures and retries”
Status Meaning What to do
400 A required field is missing or too long; error names the field. Fix the field and send again.
502 The support or roadmap service did not accept the request, so nothing was created. The body gives a general message, not the reason. Try again later. If it keeps failing, contact Replyco support with the correlationId.

Neither operation is idempotent: every successful call creates another ticket or post. Retry after a 502, never after a 200.

Operations

Section titled “Operations”
Method Path Summary Scopes
POST /openapi/support/create-ticket Create a support ticket —
POST /openapi/support/feature-requests Create a feature request —

Errors

Section titled “Errors”
Status Meaning Returned by
400 The request is invalid (e.g. subject is missing or too long).; The request is invalid (e.g. title is missing or too long). POST /openapi/support/create-ticket, POST /openapi/support/feature-requests
401 User is not authenticated or authorized. POST /openapi/support/create-ticket, POST /openapi/support/feature-requests
502 The support service is unavailable; the ticket was not created. Try again later.; The roadmap service is unavailable; the feature request was not created. Try again later. POST /openapi/support/create-ticket, POST /openapi/support/feature-requests
Section titled “Related”