Content VIllain API
  • Welcome to the API
  • Introduction
    • Introduction to the API
    • Concerns with Automating AI
    • API Technology
  • API Basics
    • Authentication
    • Error Handling
  • Email Detective
    • Email Detective Description
      • Email Detective API
  • Content Rephrasing
    • Understanding Rephrasers
      • Content Spinner API
      • NLP Rephraser API
  • Idea Generators
    • Using AI for Ideas
      • Business Ideas API
      • Blog Ideas API
      • Marketing Ideas API
      • Growth Ideas API
      • Tweet Ideas API
  • Product Descriptions
    • Sell Products with AI
      • Amazon Bullet Points
      • Ecommerce Descriptions
      • Food Product Descriptions
      • Etsy Product Descriptions
  • Blog Writing
    • Creating Blogs with AI
      • Blog Introductions
      • Section Writer
      • Blog Conclusions
      • Blog Titles & Outlines
  • Sales Copy
    • Traditional Sales Copy
      • Features, Advantages, Benefits
Powered by GitBook
On this page

Was this helpful?

  1. API Basics

Error Handling

PreviousAuthenticationNextEmail Detective Description

Last updated 3 years ago

Was this helpful?

On a successful API call, the API will return a status code of 200 and the output that has been created. Multiple outputs will be returned in an array.

You will received the following message for a wrong API key.

"Authorized": "Nope"

The possibility of a blank output is increased when a poor input is given. This follows the 'garbage in/garbage out' mantra. When multiple outputs are returned, there is also the chance for one of these to return blank. We'll be making use case examples for how to limit this happening.

Most of the time that poor outputs are given, it is due to human error. If you feel that you are providing good inputs and still receiving something unexpected, .

The other error message if something is wrong with your request will be the following;

{
    "message": "Workflow did error."
}

If you receive that error message, please check that everything is set up correctly with your API call.

reach out to us