Errors

Some errors are part of how MediSearch works. For example:

• If we do not find enough relevant articles to a question, we will return error_not_enough_articles. For example, if the question is non-medical or does not make sense, MediSearch will throw this error.
• If the conversation is too long, then we will return error_out_of_tokens. This happens very rarely in practice. It can start happening if you ask MediSearch approximately 8 questions and get 8 responses in one conversation.

Therefore, you should have at least some basic error handling mechanism to show your users a sensible message on your frontend when an error happens.

Sometimes other errors (like error_internal) can happen and these can be our fault. These errors happen fairly rarely in our experience. We are working hard for these to not happen! If you ever think that there is a problem do not hesitate to contact us: [email protected].

Event: error

Description: There was an error.

Example:

{
	event: "error",
	error_code: "some_error_code",
	id: "your_conversation_id"
}

for auth errors the id is not present and the example looks like

{
	event: "error",
	error_code: "some_error_code",
}

The possible error codes are:

error_code: error_auth

Description: You provided an incorrect API key. If you think this is a mistake, contact us!

error_code: error_missing_key

Description: The API key is missing from the request.