API Documentation
Spin Rewriter API technical documentation makes integration a breeze.
Every API request should be sent as an HTTP POST request.
Every API result is always returned in JSON format.
URL for API requests:
HTTP POST request specification:
possible values:
• api_quota
• text_with_spintax
• unique_variation
• unique_variation_from_spintax
• api_quota: returns the number of made and remaining API calls for the 24-hour period
• text_with_spintax: returns the processed spun text with spintax
• unique_variation: returns a unique variation of processed given text
• unique_variation_from_spintax: returns a unique variation of already spun text
default: (empty)
possible values:
» false (default)
» true
possible values:
• low
• medium (default)
• high
• low: largest number of synonyms for various words and phrases, least readable unique variations of text
• medium: relatively reliable synonyms, usually well readable unique variations of text (default setting)
• high: only the most reliable synonyms, perfectly readable unique variations of text
possible values:
• false (default)
• true
If set to "true", the returned spun text might contain 2 levels of nested spinning syntax.
possible values:
• false (default)
• true
If set to "true", some sentences will be replaced with a (shorter) spun variation.
possible values:
• false (default)
• true
If set to "true", some paragraphs will be replaced with a (shorter) spun variation.
possible values:
• false (default)
• true
If set to "true", the returned spun text will contain additional paragraphs.
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will change "If he is hungry, John eats." to "John eats if he is hungry." and "John eats and drinks." to "John drinks and eats."
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will never use any of the original words of phrases if there is a synonym available. This significantly improves the uniqueness of generated spun content.
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will randomize the order of paragraphs and lists where possible while preserving the readability of the text. This significantly improves the uniqueness of generated spun content.
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will make the generated spun content more human-like by applying an AI LLM model that has been fine-tuned on best-performing SEO content.
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will make the generated spun content more human-like by introducing some common typos, e.g. "teh" instead of "the".
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will make the generated spun content more human-like by introducing some common misspellings, e.g. "seperate" instead of "separate".
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will make the generated spun content more human-like by introducing some common homophone confusions, e.g. "there" instead of "their".
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will make the generated spun content more human-like by introducing some common capitalization issues, e.g. "JOhn" instead of "John".
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will make the generated spun content more human-like by introducing some common punctuation issues, e.g. "Ive" instead of "I've".
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will make the generated spun content more human-like by introducing some commonly repeated letters and words, e.g. "that that".
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will make the generated spun content more human-like by introducing some common spacing issues, e.g. two spaces after a comma.
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will add HTML code for headings (<h1>, <h2>) and lists (<ul>, <li>) that it detects in generated articles. This improves the readability of generated spun content.
possible values:
• false (default)
• true
If set to "true", Spin Rewriter will convert all line-breaks (newline characters) in generated unique articles into valid HTML tags (<br>). This lets you publish HTML code of generated unique articles without any additional work required.
possible values:
• {|} (default)
• {~}
• [|]
• [spin]
• #SPIN
• {|}: the {first option|second option} spintax used (default setting)
• {~}: the {first option~second option} spintax used
• [|]: the [first option|second option] spintax used
• [spin]: the [spin]first option|second option[/spin] spintax used
• #SPIN: the {#SPIN: first option || second option #} spintax used
JSON response specification:
Spin Rewriter API Limitations:
Spin Rewriter API comes with some limitations that allow everyone to use it reliably and without unwanted delays. At the moment you can make up to 500 API requests per day.
You should also do your best to give our API servers some rest between multiple API requests from the same application. Ideally you should make sure your individual API requests are spaced at least 7 seconds apart.
You can only submit entirely new text for processing once every 7 seconds. That's because each API request relies on the meaning-based Spin Rewriter ENL Semantic Rewriting technology that requires 40-100 times as much processing power as the more basic approach used by our competitors.
You can generate unique variations of already processed text every second though.
How to get started in 5 minutes?
Check out our collection of working API code samples. Once you see the code in action, you will feel right at home and you'll be ready to start integrating Spin Rewriter's ENL Semantic Rewriting technology into your application in no time.