API reference

Support messages

The messages in a support thread: answers, internal notes and attached files.

Base URL https://partners.monotree.com/api/v1 · every call needs a token

List messages

get /support/threads/{thread}/messages support:read

The messages of a thread, always oldest first, a page at a time. Without after or before you get the latest ones. before with the id of the first message you have walks back through a long thread; after with the id of the last one gives what is new. has_more says whether there are more on that side. This list has no cursor: next_cursor is always null.

Parameters

thread required

string · path

The thread's ID.

after

string · query

Only messages after this one. Not together with before.

before

string · query

Only messages before this one. Not together with after.

limit

integer · query

How many to return, 1 to 100.

default 50 · up to 100

Response · 200 A page of messages, oldest first.

object

string

has_more

boolean

Whether there is a page after this one.

next_cursor

string, nullable

Pass as cursor for the next page.

data

array of objects

Errors

401 invalid_token: the token is missing, revoked or expired.
403 insufficient_ability: the token lacks the ability this call needs.
404 not_found: no such support thread, or no such message in it (after, before).
422 validation_error: after and before were sent together, or limit is out of range.
429 rate_limited: too many requests. The general limit is 120 requests a minute for all your tokens of one mode (live or sandbox) together, and 300 a minute per IP address before the token is checked. Some calls have a lower limit of their own, which counts only calls that did what they ask (a call refused with another error uses up no place); the Rate limits guide lists them. Wait for the number of seconds in the Retry-After header.
curl https://partners.monotree.com/api/v1/support/threads/sth_01m7d1ajq9w7ak2vnnp8hfdwj8/messages \
  -H "Authorization: Bearer $MONOTREE_TOKEN"
200 · Response
{
    "object": "list",
    "data": [
        {
            "id": "msg_01m7d1ajqgwbvenrpw7gz6xn25",
            "object": "support_message",
            "direction": "in",
            "kind": "message",
            "author": {
                "type": "customer",
                "name": "Sophie Garnier"
            },
            "body": "Bonjour, mon invitation ne marche pas.",
            "edited": false,
            "deleted": false,
            "attachments": [],
            "delivery": null,
            "send_state": null,
            "sent_at": "2026-11-14T12:43:10Z",
            "delivered_at": null
        },
        {
            "id": "msg_01m7d1awpxds8kqrrt6733j0d2",
            "object": "support_message",
            "direction": "out",
            "kind": "message",
            "author": {
                "type": "api",
                "name": "API · Back office, production"
            },
            "body": "Bonjour Sophie, voici le guide.",
            "edited": false,
            "deleted": false,
            "attachments": [
                {
                    "id": "att_2",
                    "name": "guide.pdf",
                    "mime": "application/pdf",
                    "size": 48213,
                    "url": "https://partners.monotree.com/api/v1/support/attachments/att_2"
                }
            ],
            "delivery": {
                "state": "delivered",
                "error": null,
                "delivered_at": "2026-11-14T12:43:21Z"
            },
            "send_state": "sent",
            "sent_at": "2026-11-14T12:43:21Z",
            "delivered_at": "2026-11-14T12:43:21Z"
        }
    ],
    "has_more": false,
    "next_cursor": null
}

Only mpt_test_… tokens work here; nothing reaches a real customer. Kept in this browser tab only.

Sending…

                    

Answer a support thread

post /support/threads/{thread}/messages support:write

Sends an answer to the customer, in their Support room or by mail as the thread came. Files go in the same JSON body, base64 encoded: up to 8, together at most 25 MB before encoding. The thread becomes waiting; a closed thread opens again; a dismissed one must be reopened first. Monotree delivers the answer, and delivery.state says how far it got. With last_seen_message nothing is sent when they have written again since (409), so you never answer past a message you have not read. The assistant's drafts that were waiting are marked superseded. In a thread by mail an answer is a mail: at most 20 an hour to one thread and 200 an hour in all, and it goes to every address on copy too: at most 60 recipients an hour for one thread and 1,000 for all. By chat: 600 answers an hour. With files: 30 answers an hour and 500 MB of files a day. Only these kinds of file are taken, by the ending of the name: pdf, png, jpg, jpeg, gif, webp, heic, txt, csv, doc, docx, xls, xlsx, ppt, pptx, odt, ods, odp, rtf, mp4, mov, m4a and mp3; the content must be what the ending says, and a zip or any other kind is refused. A name is kept without control characters and at most 120 characters long. For a note only your people read, use Add a note.

Parameters

thread required

string · path

The thread's ID.

Accepts an optional Idempotency-Key header to make a retry safe.

Request body

body

string, nullable

The answer, as plain text. Needed unless there are attachments.

at most 10000 characters

attachments

array of objects

Files to send with the answer. All the files of one answer are together at most 25 MB before encoding. Each is an object with name and content only; any other field is refused.

last_seen_message

string

The latest message of theirs (direction: in) you have read. Where that is not their latest message any more, nothing is sent (409 invalid_state).

at most 40 characters

Response · 201 The thread whole, with the answer last in `messages`.

id

string

object

string

channel

string

chat: their Support room in the Monotree app. email: mail to your support address.

one of chat, email

status

string

open waits for you, waiting waits for the customer. closed is done; dismissed was never one to answer (spam, a mistake, an automatic mail).

one of open, waiting, closed, dismissed

view

string

Where the Support page shows it: the status, or snoozed for an open or waiting thread put aside until snoozed_until. Never followup: a thread under that view keeps its own view here.

one of open, waiting, snoozed, closed, dismissed

priority

string

How pressing it is. normal until the assistant reads the thread or you set it; what you set stays.

one of urgent, high, normal, low

kind

string, nullable

What the thread is. The assistant sets it when it reads the thread; what you set stays. Null until then.

one of question, bug, feature_request, other

subject

string, nullable

The subject of a mail. Null for a chat.

summary

string, nullable

What it is about, in a line, as the assistant read it.

preview

string, nullable

The start of their last message, up to 190 characters.

language

string, nullable

The language they write in, as the assistant read it.

unread

boolean

The thread is open and they have written since it was last marked read: by one of your people opening it in the portal, or by you sending unread: false.

customer

object, nullable

The customer the person belongs to. Null for a mail from a sender nobody has tied to a customer yet (live only).

id

string

company_name

string

external_ref

string, nullable

Your own reference for the customer.

person

object

Someone at a customer who wrote to support, or was written to, with what Monotree knows of them.

id

string, nullable

Null in List people for a customer's invited admin who has not written and has not been written to yet: start a thread by mail with their email.

object

string

name

string

email

string, nullable

phone

string, nullable

role

string, nullable

Their role in their company's Monotree.

title

string, nullable

Their job title.

locale

string, nullable

The language of their app.

timezone

string, nullable

departments

array of strings

The names of their departments.

device

object, nullable

The phone they last used the app on, where known.

platform

string, nullable

model

string, nullable

os

string, nullable

app_version

string, nullable

last_active_on

string, nullable

The day they last used the app.

verified

boolean

Monotree knows the sender is who they say.

chat

boolean

They have a Support room in the app and can be written to by chat.

admin

boolean

They are the admin Monotree invited at their company, who can always be written to by mail. Told in List people; false on a thread.

customer

object, nullable

Their company. Filled in List people only; null on a thread, which has its own customer.

id

string

company_name

string

assignee

object, nullable

Which of your people has the thread. Null for nobody. The first of your people to answer in the portal gets it; an answer over the API assigns nobody.

id

string

name

string

tags

array of objects

The product areas the thread is about.

cc

array of objects

Who else gets your answers to a mail. Empty for a chat.

signed

boolean

Whether your answers in this thread end with the first name of the person who wrote them. Follows the desk's signature setting for a chat and is always true for a mail, unless set on the thread.

needs_person

object, nullable

Set where the assistant, with auto on sends, did not send its draft and one of your people must look. Cleared when one of you answers.

since

string

reason

string, nullable

Why, in a sentence for your people.

no_reply_needed

boolean

The assistant read their last message as one that needs no answer (a thank-you, say).

snoozed_until

string, nullable

Until when the thread is put aside. Null when it is not, or when the time has passed.

resolution

string, nullable

How a closed thread ended: answered, no_reply (there was nothing to answer), no_response (they went quiet), outreach (a message of yours to many people, sent from the portal). Null while it is open or waiting.

dismissed_reason

string, nullable

Why it was dismissed: staff (by hand, no reason given), spam, mistake, duplicate, api (over the API, no reason given); or by the desk itself, auto (an automatic mail) or deleted (they took the message back).

rating

string, nullable

Whether your answer helped, as the customer said when the chat was closed.

one of positive, negative

rated_at

string, nullable

reopened_count

integer

How many times it was closed or dismissed and opened again.

message_count

integer

Their messages and yours together, the automatic reply included.

started_at

string, nullable

waiting_since

string, nullable

Since when their oldest unanswered message has waited. Null when nothing waits for you.

first_response_at

string, nullable

When their first message was first answered. The automatic reply does not count.

last_message_at

string, nullable

When the last message was written in it. The list is ordered by this.

closed_at

string, nullable

When it was closed or dismissed.

updated_at

string, nullable

messages

array of objects

Only on a single thread: its latest 50 messages, oldest first.

has_earlier_messages

boolean

Only on a single thread: there are messages before the ones in messages.

notes

array of objects

Only on a single thread: the notes of your people, oldest first.

history

array of objects

Only on a single thread: who did what, when, oldest first.

escalations

array of objects

Only on a single thread: what was handed on to Monotree from it.

draft

object, nullable

A draft of an answer by the assistant. Nothing in it is sent until you send it.

id

string

object

string

status

string

queued and running: the assistant is at it. ready: written. failed: it could not be written; see error. cancelled: given up.

one of queued, running, ready, failed, cancelled

round

integer

Which turn of the customer it answers: 1 for their first message.

version

integer

Which version within the round: 2 after one redraft.

trigger

string

What started it: their first message, a later one, a request for another version, a request for a draft, or the follow-up of a released escalation.

one of new, followup, redraft, manual, release

stale

boolean

They have written again since it was drafted.

body

string, nullable

The answer the assistant proposes. Null while it is being written, and where it proposes no answer.

language

string, nullable

The language of the answer.

summary

string, nullable

What the thread is about, in a line.

kind

string, nullable

What the assistant read the thread as: question, bug, feature_request or other.

no_reply_needed

boolean

The assistant read their last message as one that needs no answer. You can agree and close the thread.

confidence

string, nullable

How sure the assistant is of the draft. Null while it is being written.

one of high, medium, low

recommendation

object, nullable

What the assistant advises you to do. Null while the draft is being written.

action

string

send: send the draft. ask_customer: ask the customer for more. create_ticket: escalate to Monotree. close: close without answering. escalate: hand to Monotree now.

one of send, ask_customer, create_ticket, close, escalate

label

string

The action in words.

text

string

Why.

unverified

array of strings

What it could not check.

questions

array of objects

What the assistant would like to know from you for a better version. Answer by asking for another version with answers.

answers

array of objects

The options picked for this version.

note

string, nullable

What was asked of this version.

escalation

object, nullable

An escalation to Monotree the assistant has written out, for you to send with Escalate a thread. Null where it proposes none.

category

string

bug, feature_request or investigation.

title

string

description

string

tags

array of strings

Names of tags.

sources

array of objects

What the assistant read to write it. The shape of an entry is not settled yet; show it, do not build on it.

error

string, nullable

Why it failed. Null unless status is failed.

outcome

string, nullable

What became of it. Null while it waits for you. sent_unchanged, edited, replaced: it was sent, as written, changed, or mostly rewritten. discarded: put aside. superseded: an answer went out another way, or a draft for their next turn replaced it. no_reply_accepted: the thread was closed on it.

one of sent_unchanged, edited, replaced, discarded, superseded, no_reply_accepted

created_at

string, nullable

finished_at

string, nullable

When the assistant was done with it.

Errors

400 invalid_idempotency_key: the Idempotency-Key is longer than 255 characters.
401 invalid_token: the token is missing, revoked or expired.
403 insufficient_ability: the token lacks the ability this call needs.
404 not_found: no such support thread, or last_seen_message is not a message of it.
409 invalid_state: they have written again since last_seen_message, the thread is dismissed, or it is a mail thread with an address that has never written in and is no longer the admin Monotree invited (a token cannot write to it). idempotency_in_progress: a call with the same Idempotency-Key is still running.
422 validation_error: neither body nor attachments, more than 8 files, a file that is not base64 or is empty, files that are together larger than 25 MB, an attachment with a field other than name and content, or a file of a kind that is not taken (anything but the kinds listed above, or content that is not what the name says). idempotency_key_reused: the Idempotency-Key was used for a different request.
429 rate_limited: in a thread by mail, more than 20 answers to this thread or 200 answers by mail in all in an hour (all your tokens of one mode together), or more recipients than 60 for the thread or 1,000 in all; by chat more than 600 answers an hour; with files more than 30 answers an hour or 500 MB a day; or over the general limit. Wait for the number of seconds in Retry-After where there is one, else a few minutes.
curl -X POST https://partners.monotree.com/api/v1/support/threads/sth_01m7d1ajq9w7ak2vnnp8hfdwj8/messages \
  -H "Authorization: Bearer $MONOTREE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "body": "Bonjour Sophie, voici le guide.",
    "last_seen_message": "msg_01m7d1ajqgwbvenrpw7gz6xn25",
    "attachments": [
        {
            "name": "guide.pdf",
            "content": "JVBERi0xLjQK"
        }
    ]
}'
201 · Response
{
    "id": "sth_01m7d1ajq9w7ak2vnnp8hfdwj8",
    "object": "support_thread",
    "channel": "chat",
    "status": "waiting",
    "view": "waiting",
    "priority": "high",
    "kind": "bug",
    "subject": null,
    "summary": null,
    "preview": "Bonjour, mon invitation ne marche pas.",
    "language": "fr",
    "unread": false,
    "customer": {
        "id": "cus_01jcz8w3k1x9q2v7s4e6m0b5n8",
        "company_name": "Boulangerie Martin",
        "external_ref": "org_48213"
    },
    "person": {
        "id": "per_132",
        "object": "support_person",
        "name": "Sophie Garnier",
        "email": "sophie@boulangeriemartin.example",
        "phone": null,
        "role": "Manager",
        "title": null,
        "locale": "fr",
        "timezone": null,
        "departments": [],
        "device": null,
        "last_active_on": null,
        "verified": true,
        "chat": true,
        "customer": null
    },
    "assignee": {
        "id": "sel_5",
        "name": "Emma Dubois"
    },
    "tags": [
        {
            "id": 1,
            "name": "Invitations",
            "color": "#0e7490"
        }
    ],
    "cc": [],
    "signed": true,
    "needs_person": null,
    "no_reply_needed": false,
    "snoozed_until": null,
    "resolution": null,
    "dismissed_reason": null,
    "rating": null,
    "rated_at": null,
    "reopened_count": 0,
    "message_count": 2,
    "started_at": "2026-11-14T12:43:10Z",
    "waiting_since": null,
    "first_response_at": "2026-11-14T12:43:21Z",
    "last_message_at": "2026-11-14T12:43:21Z",
    "closed_at": null,
    "updated_at": "2026-11-14T12:44:09Z",
    "messages": [
        {
            "id": "msg_01m7d1ajqgwbvenrpw7gz6xn25",
            "object": "support_message",
            "direction": "in",
            "kind": "message",
            "author": {
                "type": "customer",
                "name": "Sophie Garnier"
            },
            "body": "Bonjour, mon invitation ne marche pas.",
            "edited": false,
            "deleted": false,
            "attachments": [],
            "delivery": null,
            "send_state": null,
            "sent_at": "2026-11-14T12:43:10Z",
            "delivered_at": null
        },
        {
            "id": "msg_01m7d1awpxds8kqrrt6733j0d2",
            "object": "support_message",
            "direction": "out",
            "kind": "message",
            "author": {
                "type": "api",
                "name": "API · Back office, production"
            },
            "body": "Bonjour Sophie, voici le guide.",
            "edited": false,
            "deleted": false,
            "attachments": [
                {
                    "id": "att_2",
                    "name": "guide.pdf",
                    "mime": "application/pdf",
                    "size": 48213,
                    "url": "https://partners.monotree.com/api/v1/support/attachments/att_2"
                }
            ],
            "delivery": {
                "state": "delivered",
                "error": null,
                "delivered_at": "2026-11-14T12:43:21Z"
            },
            "send_state": "sent",
            "sent_at": "2026-11-14T12:43:21Z",
            "delivered_at": "2026-11-14T12:43:21Z"
        }
    ],
    "has_earlier_messages": false,
    "notes": [
        {
            "id": "note_2",
            "object": "support_note",
            "author": {
                "type": "api",
                "name": "API · Back office, production"
            },
            "body": "Called the manager; she will try again on Monday.",
            "created_at": "2026-11-14T12:43:20Z"
        }
    ],
    "history": [
        {
            "type": "opened",
            "by": null,
            "details": null,
            "at": "2026-11-14T12:43:10Z"
        },
        {
            "type": "assigned",
            "by": "API · Back office, production",
            "details": {
                "assignee": "Emma Dubois"
            },
            "at": "2026-11-14T12:44:09Z"
        }
    ],
    "escalations": [
        {
            "id": "esc_01m7d1cbwj6agthjesfk7198t7",
            "title": "Invitation link opens a blank page",
            "category": "bug",
            "status": "sent",
            "relation": "created",
            "released_in": null,
            "follow_up_due": false,
            "followed_up_at": null,
            "follow_up_outcome": null
        }
    ],
    "draft": {
        "id": "drf_227",
        "object": "support_draft",
        "status": "ready",
        "round": 1,
        "version": 1,
        "trigger": "new",
        "stale": false,
        "body": "Bonjour Sophie,\n\nMerci pour votre message.\n\nEssayez d'abord de vous déconnecter puis de vous reconnecter, et vérifiez que l'application Monotree est à jour.",
        "language": "fr",
        "summary": null,
        "kind": "bug",
        "no_reply_needed": false,
        "confidence": "medium",
        "recommendation": {
            "action": "create_ticket",
            "label": "Escalate to Monotree",
            "text": "This sounds like a fault in the app rather than a question. Send the first steps, and escalate it to Monotree if they do not help.",
            "unverified": [
                "Whether it happens on every phone or only one kind."
            ]
        },
        "questions": [],
        "answers": [],
        "note": null,
        "escalation": null,
        "sources": [],
        "error": null,
        "outcome": "superseded",
        "created_at": "2026-11-14T12:43:10Z",
        "finished_at": "2026-11-14T12:43:10Z"
    }
}

Only mpt_test_… tokens work here; nothing reaches a real customer. Kept in this browser tab only.

Sending…

                    

Send a failed answer again

post /support/threads/{thread}/messages/{message}/retry support:write

An answer whose delivery.state is failed is handed to Monotree again. It is the same message, so nothing arrives twice. No body is needed.

Parameters

thread required

string · path

The thread's ID.

message required

string · path

The message's ID. It must be a message of the thread in the path.

Accepts an optional Idempotency-Key header to make a retry safe.

Response · 200 The answer, on its way again.

id

string

object

string

direction

string

in: theirs. out: from your desk.

one of in, out

kind

string

auto: the automatic reply sent while the desk was offline. It does not count as an answer.

one of message, auto

author

object

type

string

customer: someone at the customer. seller: one of your people, in the portal. api: a token of yours. assistant: the assistant sending its own draft (auto on sends). system: the desk itself (the automatic reply).

one of customer, seller, api, assistant, system

name

string, nullable

The person's name; API · and the token's name; the name the assistant goes by; or Support for the desk.

body

string, nullable

The text, as plain text. Null where they took the message back.

edited

boolean

They changed the message after sending it.

deleted

boolean

They took the message back. Its body is then null and its attachments empty.

attachments

array of objects

delivery

object, nullable

How far an answer got. Null on their messages.

state

string

sending: on its way to Monotree. sent: with Monotree. delivered: it reached them. failed: it could not be delivered; see error and send it again.

one of sending, sent, delivered, failed

error

string, nullable

Why it failed. Null unless state is failed.

delivered_at

string, nullable

send_state

string, nullable

Older than delivery, kept for now: use delivery.state. Null on their messages.

one of sending, sent, failed

sent_at

string, nullable

When it was written. Messages are ordered by this.

delivered_at

string, nullable

The same as delivery.delivered_at: use that.

Errors

400 invalid_idempotency_key: the Idempotency-Key is longer than 255 characters.
401 invalid_token: the token is missing, revoked or expired.
403 insufficient_ability: the token lacks the ability this call needs.
404 not_found: no such support thread, or no such message in it.
409 invalid_state: the message is not an answer of yours that failed. idempotency_in_progress: a call with the same Idempotency-Key is still running.
422 idempotency_key_reused: the Idempotency-Key was used for a different request.
429 rate_limited: in a thread by mail this counts as an answer (20 an hour to one thread, 200 an hour in all); or over the general limit. Wait for the number of seconds in Retry-After.
curl -X POST https://partners.monotree.com/api/v1/support/threads/sth_01m7d1ajq9w7ak2vnnp8hfdwj8/messages/msg_01m7d1awpxds8kqrrt6733j0d2/retry \
  -H "Authorization: Bearer $MONOTREE_TOKEN"
200 · Response
{
    "id": "msg_01m7d1awpxds8kqrrt6733j0d2",
    "object": "support_message",
    "direction": "out",
    "kind": "message",
    "author": {
        "type": "api",
        "name": "API · Back office, production"
    },
    "body": "Bonjour Sophie, voici le guide.",
    "edited": false,
    "deleted": false,
    "attachments": [],
    "delivery": {
        "state": "sent",
        "error": null,
        "delivered_at": null
    },
    "send_state": "sent",
    "sent_at": "2026-11-14T12:43:21Z",
    "delivered_at": null
}

Only mpt_test_… tokens work here; nothing reaches a real customer. Kept in this browser tab only.

Sending…

                    

Add a note

post /support/threads/{thread}/notes support:write

A note on the thread for your own people. The customer never sees it, and it does not change the thread's status. Notes come back in the thread's notes, oldest first; a note cannot be changed or removed. Sends support.thread.updated with change: noted.

Parameters

thread required

string · path

The thread's ID.

Accepts an optional Idempotency-Key header to make a retry safe.

Request body

body required

string

The note, as plain text.

at most 10000 characters

Response · 201 The note.

id

string

object

string

author

object

type

string

seller: one of your people, in the portal. api: a token of yours.

one of seller, api

name

string, nullable

body

string

created_at

string, nullable

Errors

400 invalid_idempotency_key: the Idempotency-Key is longer than 255 characters.
401 invalid_token: the token is missing, revoked or expired.
403 insufficient_ability: the token lacks the ability this call needs.
404 not_found: no such support thread for your company and mode.
409 idempotency_in_progress: a call with the same Idempotency-Key is still running.
422 validation_error: body is missing, empty or longer than 10,000 characters. idempotency_key_reused: the Idempotency-Key was used for a different request.
429 rate_limited: too many requests. The general limit is 120 requests a minute for all your tokens of one mode (live or sandbox) together, and 300 a minute per IP address before the token is checked. Some calls have a lower limit of their own, which counts only calls that did what they ask (a call refused with another error uses up no place); the Rate limits guide lists them. Wait for the number of seconds in the Retry-After header.
curl -X POST https://partners.monotree.com/api/v1/support/threads/sth_01m7d1ajq9w7ak2vnnp8hfdwj8/notes \
  -H "Authorization: Bearer $MONOTREE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "body": "Called the manager; she will try again on Monday."
}'
201 · Response
{
    "id": "note_2",
    "object": "support_note",
    "author": {
        "type": "api",
        "name": "API · Back office, production"
    },
    "body": "Called the manager; she will try again on Monday.",
    "created_at": "2026-11-14T12:43:20Z"
}

Only mpt_test_… tokens work here; nothing reaches a real customer. Kept in this browser tab only.

Sending…

                    

Download an attachment

get /support/attachments/{attachment} support:read

The file itself, for a token that may read its thread. This is what url points to on a file sent with one of your answers: fetch it with your token in the Authorization header. A PNG, JPEG, GIF or WebP picture comes with its own content type; anything else as application/octet-stream with the file's name in Content-Disposition. A file the customer sent is kept by Monotree: its url is that address, and this endpoint redirects to it. The answer says Cache-Control: private, no-store: do not keep it in a shared cache.

Parameters

attachment required

string · path

The file's ID, from a message's attachments.

Errors

401 invalid_token: the token is missing, revoked or expired.
403 insufficient_ability: the token lacks the ability this call needs.
404 not_found: no such attachment in a thread of your company and mode.
429 rate_limited: too many requests. The general limit is 120 requests a minute for all your tokens of one mode (live or sandbox) together, and 300 a minute per IP address before the token is checked. Some calls have a lower limit of their own, which counts only calls that did what they ask (a call refused with another error uses up no place); the Rate limits guide lists them. Wait for the number of seconds in the Retry-After header.
curl https://partners.monotree.com/api/v1/support/attachments/att_2 \
  -H "Authorization: Bearer $MONOTREE_TOKEN"

Only mpt_test_… tokens work here; nothing reaches a real customer. Kept in this browser tab only.

Sending…