Random Anagram API

The random anagram API generates a anagram and answer pair at random. It can be requested to return anagrams of varying difficulty levels from easy to hard.

On this page

• Consuming the API
• Endpoint Open API Specification
• Example Request
• Request Parameters
• Example Response

Consuming the API

• Navigate to the Word Checker Rapid API page.
• You will need to setup a Rapid API account and application to use our APIs. We offer a free subscription package on Rapid API, however, you may need to switch to a paid subscription if your application traffic grows.
• Click on the endpoint titled GET Random Anagram Generator section.

Endpoint Open API Specification

openapi: 3.0.4

info:
  title: Word Checker Service
  description: API of word tools such as anagram solvers, random word generators, and more.
  version: 1.0.0

paths:
  /v1/generator/random-anagram:
    get:
      summary: Random Anagram Generator
      parameters:
        - name: difficulty
          in: query
          description: The difficulty of the anagram to solve
          required: true
          schema:
            type: string
            enum:
              - easy
              - medium
              - hard
      responses:
        "200":
          description: A JSON object containing the random anagram
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/RandomAnagramResponse"
        "400":
          $ref: "#/components/responses/ErrorResponse"
        "429":
          $ref: "#/components/responses/TooManyRequests"

components:
  responses:
    ErrorResponse:
      description: A generic error responses with error code and hint
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                description: The error code
                type: string
                example: ERROR_CODE
              error_hint:
                description: A hint to resolve the error
                type: string
                example: Error hint
            required:
              - error
              - error_hint
    TooManyRequests:
      description: Too Many Requests
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                description: The error code
                type: string
                example: TOO_MANY_REQUESTS
              error_hint:
                description: A hint to resolve the error
                type: string
                example: You're making requests a bit too quickly. Please wait a moment and try again.
            required:
              - error
              - error_hint
  schemas:
    RandomAnagramResponse:
      type: object
      properties:
        anagram:
          description: The random anagram generated
          type: string
          example: LEOHL
        answer:
          description: The random anagram unscrambled to the original word
          type: string
          example: HELLO
      required:
        - anagram
        - answer

Example Request

curl --request GET \
	--url 'https://word-checker-api.p.rapidapi.com/v1/generator/random-anagram?difficulty=$DIFFICULTY' \
	--header 'x-rapidapi-host: word-checker-api.p.rapidapi.com' \
	--header 'x-rapidapi-key: $YOUR_RAPID_API_KEY'

Request Parameters

Query Parameters

• DIFFICULTY: The difficulty of the anagram to solve (must be one of easy, medium, or hard).

Headers

• YOUR_RAPID_API_KEY: You’re Rapid API key to authenticate the request. See Rapid APIs docs.

Example Response

A successful response will be a JSON object containing an anagram (the jumbled up letters) and answer (the solution).

{ "anagram": "HTNRO", "answer": "NORTH" }

If a response is unsuccessful, a standard error response will be returned. For example, the below represents an INVALID_DIFFICULTY error.

{
  "error": "INVALID_DIFFICULTY",
  "error_hint": "The difficulty provided is invalid."
}

The error_hint is meant for the application/server and may not always make sense to display to the end user.