Skip to content
ReplycoReplycoAPI

Folders

A folder is a label your team puts on tickets, such as “Refunds” or “VIP”, so that they can find and group them in the Replyco inbox. A ticket can be in several folders. Your team manages folders in the Replyco app; the API reads them, to turn a folder’s name into the id that other operations take.

Fields that matter

Section titled “Fields that matter”
Field Meaning
id The folder’s id. Pass it as folderId to put tickets in the folder, or to an automation rule.
name The folder’s name, as your team sees it in the app.

Listing

Section titled “Listing”

GET /openapi/folder returns the folders available to the user your token belongs to, in the order they appear in the app. Folders the user does not have are not in the list, so sign in as a user who has the folders your integration needs. The list has no pages and takes no parameters; it is an empty array when the user has no folders.

Terminal window
curl https://open-api.replyco.com/openapi/folder -H "Authorization: Bearer $ACCESS_TOKEN"
[
  { "id": "0b4e6c1d-2f3a-4b5c-9d8e-7f6a5b4c3d2e", "name": "Refunds" },
  { "id": "8c2f4a6b-1d3e-4f5a-9b7c-6d8e0f1a2b3c", "name": "VIP" }
]

GET /openapi/folder/{id} returns one of those folders. Any other id is answered with 404.

Look the folders up once per run and reuse the ids, rather than asking again for every ticket.

Operations

Section titled “Operations”
Method Path Summary Scopes
GET /openapi/folder List my folders (labels) —
GET /openapi/folder/{id} Get one of my folders (labels) —

Errors

Section titled “Errors”
Status Meaning Returned by
401 User is not authenticated or authorized. GET /openapi/folder, GET /openapi/folder/{id}
404 No such folder is available to the current user. GET /openapi/folder/{id}
Section titled “Related”