# Request online payments help

Source: https://api-docs.magicdoor.com/api-reference/sales-inquiries/request-online-payments-help

Tells MagicDoor's customer success team that the company wants help getting more of its tenants paying online, and passes along the company and the caller so they can get in touch.

`POST https://services.magicdoor.com/salesworkflows/company-portal/sales-inquiries/online-payments-help`

**Authentication:** bearer token in the `Authorization` header, as `Bearer <token>`.

## Body

Content type: `application/json`

An optional note. Everything else the team needs — which company asked, and who — is taken from the access token.

- `message` (string) — What the caller wants help with, in their own words. Passed on as written. Leave it out or send it empty and the request is still delivered, just without a note.

```json
{
  "message": "About half our tenants still mail checks. What has worked for other managers?"
}
```

## Example request

```bash
curl --request POST \
  --url 'https://services.magicdoor.com/salesworkflows/company-portal/sales-inquiries/online-payments-help' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "message": "About half our tenants still mail checks. What has worked for other managers?"
}'
```

## Responses

### 200 — The request has been handed to MagicDoor's customer success team. There is no body, and nothing is recorded on the company's account for you to read back — treat a 200 as "they know".

### 401 — The access token is missing, expired, or not valid.

> **Note: Nothing to poll**
>
> This is a one-way message to a person, not a ticket. There is no id to follow up on and no status to check — someone gets in touch. Show the user a confirmation and leave it there.
