The chat app’s details are not complete

View as MarkdownJSONAsk Xovris about it

What your request got backHTTP 400
{
  "type": "https://xovris.ai/problems/invalid-chat",
  "title": "Discord needs the bot's token",
  "status": 400,
  "next": "Send reply as the https address the chat gives an incoming webhook, or leave it out - Xovris answers in the outgoing webhook's own reply then."
}
  1. typeNames this page
  2. titleWhat was refused
  3. statusThe HTTP status the answer comes with, 400
  4. nextYour next step
Drawn from the Xovris API’s own error catalogue – the answer as a client receives it

What happened, and what to do next

Every case this type is answered with, in the answer’s own words, each with its next step.

An answer of this type carries one of 4 titles – yours is the one in your answer:

  • Discord needs the bot's token
  • Google Chat needs the project number and the Chat app's service account key
  • The chat's incoming address is not a public web address, so Xovris kept nothing
  • The members list is not right, so Xovris kept nothing
  1. What to do next

    Your answer’s own “next” line is the step for your case. This type gives one of these:

    Send reply as the https address the chat gives an incoming webhook, or leave it out - Xovris answers in the outgoing webhook's own reply then.

    PUT /v1/reviews/chats with members as the body below, or leave it out.

    Request bodyPUT /v1/reviews/chats
    [  {    "user": "<platform user>",    "member": "<member id>"  }]
  2. What happened

    Nothing was kept.

    What to do next

    Your answer’s own “next” line is the step for your case. This type gives one of these:

    PUT /v1/reviews/chats with the body below - the token on the Bot page of your application in Discord's Developer Portal. Xovris reads the rest itself.

    Request bodyPUT /v1/reviews/chats
    {  "platform": "discord",  "token": "..."}

    PUT /v1/reviews/chats with the body below - the number on the Google Cloud project's dashboard and the JSON key of the service account the Chat app runs as.

    Request bodyPUT /v1/reviews/chats
    {  "platform": "google-chat",  "project": "123456789012",  "serviceAccount": {...}}

Send the request, see what the API answers

The requests that can get this answer, sent from this page to the live API. Your key, if you give one, goes to the API alone and is never kept.

Try the request

Without a key the API answers as it does to anyone not signed in. The key is sent to api.xovris.ai alone and kept nowhere.

Sent from your browser to api.xovris.ai - the answer is exactly what it sent

What your request got, decoded in your browser

The whole answer, its type link or a status code. It is read in this browser and sent nowhere.

Read your answer

It stays in your browser and is sent nowhere.

Read in this browser – nothing you paste leaves it

Every other type 150 the API can answer with

This kind first, then the rest – type any word, status or name to find one.

Something in the request needs changing · 58 types
Sign-in needed · 2 types
Not allowed for your role · 4 types
Not found · 16 types
No longer there · 2 types
Conflicts with how things are now · 46 types
A service Xovris relies on did not answer · 21 types
Not switched on at this server yet · 1 type

Still stuck?

The status page says whether Xovris knows of a wider fault. Support can look at your case: send the answer you got and what you were doing.

Open the status pageWrite to supportAll problem types

This is how Xovris answers a request it says no to: at the moment you ask, with its reason. The answer above is the whole of it.

Words on this page, in plain English

Each technical word this page uses, said simply.

Web connection (HTTP)
The way a browser asks a website for a page and the website answers.
Secure web connection (HTTPS)
The encrypted way a browser and a website talk, so nobody on the way can read or change what passes – the padlock in a browser.
A message sent to your own system (webhook, webhooks)
An automatic message one service sends to an address you choose the moment something happens.
Program-to-program connection (API, APIs)
A way for one program to ask another for information or to do something, without a person clicking through a website.

Ask Xovris

Open the full page