Guide· How do I…?Draft

Contact Gitmoap

On this page you can1 task

Send a message

1 endpoint Limits TroubleshootingShow tasks as

Overview

You can write to a person at Gitmoap from the contact form, signed in or not. Choose what your message is about — help with using Gitmoap, a privacy request, a legal notice, a report of illegal content, or a security vulnerability — and it goes to the desk that handles it. A person reads it, and any reply comes by email to the address you give.

Nothing is sent to that address unless a person replies: no confirmation email, no copy of your message. The form answers at once with a reference, which you quote if you write again about the same thing. The desks' own email addresses, listed in the Entity Details of our legal documents, reach the same people if you prefer to write directly.

Before you start

An email address you read.It is where the reply goes, and the only way we can answer you.
No account is needed.If you are signed in, the message records which account sent it, which helps the desk answer a question about it.

How it works

The form sends your message to one of Gitmoap's own mailboxes, chosen by its topic:

Topic	Who reads it
`support`	Support: questions about using Gitmoap
`privacy`	Privacy requests: access to, correction or deletion of your personal data
`legal`	Notices: legal correspondence
`abuse`	Reports of illegal content
`security`	Security disclosures

Your message usually reaches the desk within a few minutes. We keep the form's own record of it — the topic, your address, your name if you gave it, the message, and the account you were signed in with — for 30 days after it reached the desk, and then delete it; the conversation that follows lives in the desk's mailbox, under the retention our Privacy Statement gives for messages sent to us. To limit how many messages one place on the internet can send, we keep a one-way fingerprint of the network you wrote from — never the address itself.

A report about the platform — a bug, a missing capability — is quicker through Report a problem, which needs no reply.

How to

Send a message

Select Contact gitmoap below the sign-in form or any other signed-out page, Contact a person in the help panel, or Contact gitmoap in your account menu — or go to https://gitmoap.com/-/contact. Choose a topic, give your email address, write your message and send it. The confirmation shows the reference to quote.

Terminalbash

gitmoap contact submit-contact-message \

--email <email> \

--message <message> \

--topic support|privacy|legal|abuse|security

curlbash

curl -X POST https://api.gitmoap.example/contact \

-H "Content-Type: application/json" \

-d '{ "email": "<string>", "message": "<string>", "topic": "<one of abuse | legal | privacy | security | support>" }'

Reference

1 endpoint

POST/contactpublic

Send a message to a person at Gitmoap

submit_contact_messagePOST /contactOpen in the API reference

Token scope

None — this one is public

Counts against

contact_messages_per_source_hour

Send

Body

emailstringOne email address the reply goes to, such as ada@example.com — never a list, and never a name with an address.
messagestringWhat you want to say: 10 to 5000 characters, with no control characters but newlines and tabs.
nameobjectoptional
topicabuselegalprivacysecuritysupportWhat a message is about, which chooses the desk it is forwarded to.
websiteobjectoptionalLeave empty. A form a person fills in never sets it.

Refuses

400A field is not valid
413The request body is too large
429Several messages were sent recently; try again later
501The contact form is not available on this deployment

Receive

message_iduuidThe reference of a message sent through the contact form — quote it if you write again about the same thing.
received_atstringWhen the message arrived.

Limits

What	Limit
Messages from one network	5 in any hour
Messages across Gitmoap	200 in any 24 hours
Message	10 to 5000 characters
Name	1 to 100 characters, optional
Email address	one address, such as `ada@example.com`
How long the form's record is kept	30 days after the message reached its desk

Past either cap the form answers 429 TOO_MANY_REQUESTS with a Retry-After header saying how many seconds to wait. The desks' email addresses are never capped.

Troubleshooting

Symptom	Cause	What to do
400— `message must be 10 to 5000 characters`	The message is too short to answer, or too long	Say what you need in a few sentences
400— `email must be one address`	The address field holds a list, or a name and an address	Give one address and nothing else
413 PAYLOAD_TOO_LARGE	The request is far larger than any message	Send the fields the form asks for, and nothing more
429 TOO_MANY_REQUESTS	Five messages were sent from your network in the last hour, or Gitmoap has received as many as it takes in a day	Wait the seconds `Retry-After` gives, or write to the desk's email address
501 NOT_IMPLEMENTED	This Gitmoap environment has no contact form	Write to the desk's email address

400— message must be 10 to 5000 characters

Cause: The message is too short to answer, or too long
What to do: Say what you need in a few sentences

400— email must be one address

Cause: The address field holds a list, or a name and an address
What to do: Give one address and nothing else

413 PAYLOAD_TOO_LARGE

Cause: The request is far larger than any message
What to do: Send the fields the form asks for, and nothing more

429 TOO_MANY_REQUESTS

Cause: Five messages were sent from your network in the last hour, or Gitmoap has received as many as it takes in a day
What to do: Wait the seconds Retry-After gives, or write to the desk's email address

501 NOT_IMPLEMENTED

Cause: This Gitmoap environment has no contact form
What to do: Write to the desk's email address

Feedback about Gitmoapreporting a bug or a missing capability, with no reply needed
Your accountyour profile and the email address on it