Fortune Cookie Generator API

GET

Serve fresh fortune cookie advice, humor, and predictions.

Fortune Cookie Generator creates authentic fortune cookie messages including wisdom, predictions, advice, humor, and motivational quotes.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/fortunecookie

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "fortune": "The best time to plant a tree was 20 years ago. The second best time is now.",
    "type": "wisdom"
  }
}

About the Fortune Cookie Generator API

A free fortune cookie quotes API: each GET request returns one fortune message and its category as JSON, ready for games, entertainment apps, or a fortune cookie of the day feature.

What people use it for

Gaming Features: Add fortune cookie features to games with randomized fortune messages for enhanced player engagement
Daily Wisdom: Generate daily wisdom messages and inspirational quotes for apps, websites, and digital products
Motivational Content: Create motivational content and positive affirmations for wellness apps, productivity tools, and lifestyle platforms
Entertainment Apps: Build entertainment and novelty features with authentic fortune cookie messages

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Fortune Cookie Generator

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit

Questions.

Common questions about the Fortune Cookie Generator API.

Read the docs →

What kinds of fortunes does the generator produce?

The generator creates authentic messages across five categories: wisdom, predictions, advice, humor, and motivational quotes. Each response delivers the fortune text along with the category type it belongs to.

Can I filter fortunes by specific categories?

No, the endpoint does not accept category filters or query parameters. It returns a generated fortune from across its full catalog with each request. You can check the returned type field in your code if your app needs to filter or route messages.

Do the fortunes come with lucky numbers?

No. Each response returns the fortune text and its category type only. If your app shows lucky numbers on the cookie slip, generate them separately in your own code.

Can I request multiple fortune cookie messages at once?

No, each call delivers a single fortune message. If you want to present multiple fortunes to a user or cache a small batch, make separate calls for each fortune you need.

What would 20,000 fortune cookie messages a month cost me?

That volume uses 20,000 credits, which uses about a tenth of the Starter plan's 200,000 monthly credits. At 1 credit per call, usage works out to about $0.15 per 1,000 calls under Starter. For development and small tests, the Free plan includes 200 calls every month.

Request parameters — GET /v1/fortunecookie

This endpoint takes no parameters

Call it with your key and nothing else. Any query string you send is ignored rather than rejected.

Example request

1
2

curl "https://api.apiverve.com/v1/fortunecookie" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/fortunecookie

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "fortune": "The best time to plant a tree was 20 years ago. The second best time is now.",
    "type": "wisdom"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`fortune`	string	`"The best time to plant a tree was 20 years ago. The second best time is now."`	Generated fortune cookie message text content
`type`	string	`"wisdom"`	Category type of the generated fortune message

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 1 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Fortune Cookie Generator calls	Per 1,000 calls
Free	Free	200	200	Free
Starter	$29.99	200,000	200,000	$0.15
Pro	$99.99	1,000,000	1,000,000	$0.10
Mega	$299.99	4,000,000	4,000,000	$0.07

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/fortunecookie

No SDK to install — this is a plain HTTPS call to /v1/fortunecookie with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/fortunecookie" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/fortunecookie-apiSource, issues and the examples this page is built from.ReferenceFortune Cookie Generator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/fortunecookienpm APIVerve.API.FortuneCookieGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/fortunecookie

Install the Node.js SDK, then call the Fortune Cookie Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/fortunecookie

Node.js

const res = await fetch("https://api.apiverve.com/v1/fortunecookie", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/fortunecookieThe published Node.js client, versioned and signed.GitHubapiverve/fortunecookie-apiSource, issues and the examples this page is built from.ReferenceFortune Cookie Generator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.FortuneCookieGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/fortunecookie

No SDK to install — this is a plain HTTPS call to /v1/fortunecookie with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/fortunecookie",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/fortunecookienpm APIVerve.API.FortuneCookieGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/fortunecookie

Install the C# / .NET SDK, then call the Fortune Cookie Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.FortuneCookieGenerator

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/fortunecookie");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.FortuneCookieGeneratorThe published C# / .NET client, versioned and signed.GitHubapiverve/fortunecookie-apiSource, issues and the examples this page is built from.ReferenceFortune Cookie Generator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/fortunecookienpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/fortunecookie

No SDK to install — this is a plain HTTPS call to /v1/fortunecookie with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/fortunecookie", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/fortunecookienpm APIVerve.API.FortuneCookieGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/fortunecookie

No SDK to install — this is a plain HTTPS call to /v1/fortunecookie with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/fortunecookie");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/fortunecookienpm APIVerve.API.FortuneCookieGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/fortunecookie

No SDK to install — this is a plain HTTPS call to /v1/fortunecookie with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/fortunecookie")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body