Card Deck Shuffler is a tool for shuffling standard playing card decks. It supports multiple decks, optional jokers, and different shuffling methods to generate randomized card sequences for games and simulations.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Card Deck Shuffler response payload
}
}
About the Card Deck Shuffler API
Card Deck Shuffler works by generating standard 52-card decks and applying shuffling algorithms. Supports up to 10 decks, optional jokers, and returns complete shuffled deck with sample hands and card details.
What people use it for
- Card Games
- Generate shuffled decks for online card games, poker, and blackjack applications
- Simulations
- Simulate card distributions and test card game probabilities with random shuffles
- Game Development
- Implement card shuffling functionality in gaming applications and virtual casinos
- Teaching Tools
- Demonstrate shuffling algorithms and randomization concepts in educational applications
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
Other ways to use Card Deck Shuffler
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Card Deck Shuffler API do?
How do I authenticate Card Deck Shuffler API requests?
How much does the Card Deck Shuffler API cost?
How fast is the Card Deck Shuffler API?
What response formats does the Card Deck Shuffler API support?
What HTTP method does the Card Deck Shuffler API use?
Request parameters — GET /v1/carddeckshuffler
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
decksOptional | integer | 1 | Number of decks to shuffle default 1 · range 1-10 |
jokersOptional | boolean | false | Include jokers in the deck default false |
methodOptional | string | fisher-yates | Shuffling methodfisher-yatesriffledefault fisher-yates |
curl "https://api.apiverve.com/v1/carddeckshuffler?decks=1&jokers=false&method=fisher-yates" \
-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-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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/carddeckshuffler
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.
{
"status": "ok",
"error": null,
"data": {
"total_cards": 52,
"decks_used": 1,
"includes_jokers": false,
"shuffle_method": "fisher-yates",
"cards": [
{
"rank": "8",
"suit": "Spades",
"card": "8 of Spades",
"short": "8♠"
},
{
"rank": "2",
"suit": "Spades",
"card": "2 of Spades",
"short": "2♠"
},
{
"rank": "Queen",
"suit": "Hearts",
"card": "Queen of Hearts",
"short": "Q♥"
},
{
"rank": "7",
"suit": "Clubs",
"card": "7 of Clubs",
"short": "7♣"
},
{
"rank": "Queen",
"suit": "Spades",
"card": "Queen of Spades",
"short": "Q♠"
},
{
"rank": "King",
"suit": "Hearts",
"card": "King of Hearts",
"short": "K♥"
},
{
"rank": "6",
"suit": "Spades",
"card": "6 of Spades",
"short": "6♠"
},
{
"rank": "Queen",
"suit": "Diamonds",
"card": "Queen of Diamonds",
"short": "Q♦"
},
{
"rank": "King",
"suit": "Diamonds",
"card": "King of Diamonds",
"short": "K♦"
},
{
"rank": "4",
"suit": "Hearts",
"card": "4 of Hearts",
"short": "4♥"
},
{
"rank": "7",
"suit": "Hearts",
"card": "7 of Hearts",
"short": "7♥"
},
{
"rank": "8",
"suit": "Clubs",
"card": "8 of Clubs",
"short": "8♣"
},
{
"rank": "4",
"suit": "Spades",
"card": "4 of Spades",
"short": "4♠"
},
{
"rank": "9",
"suit": "Hearts",
"card": "9 of Hearts",
"short": "9♥"
},
{
"rank": "Ace",
"suit": "Diamonds",
"card": "Ace of Diamonds",
"short": "A♦"
},
{
"rank": "Jack",
"suit": "Diamonds",
"card": "Jack of Diamonds",
"short": "J♦"
},
{
"rank": "Jack",
"suit": "Hearts",
"card": "Jack of Hearts",
"short": "J♥"
},
{
"rank": "2",
"suit": "Clubs",
"card": "2 of Clubs",
"short": "2♣"
},
{
"rank": "Jack",
"suit": "Clubs",
"card": "Jack of Clubs",
"short": "J♣"
},
{
"rank": "Queen",
"suit": "Clubs",
"card": "Queen of Clubs",
"short": "Q♣"
},
{
"rank": "9",
"suit": "Spades",
"card": "9 of Spades",
"short": "9♠"
},
{
"rank": "8",
"suit": "Diamonds",
"card": "8 of Diamonds",
"short": "8♦"
},
{
"rank": "10",
"suit": "Spades",
"card": "10 of Spades",
"short": "10♠"
},
{
"rank": "9",
"suit": "Clubs",
"card": "9 of Clubs",
"short": "9♣"
},
{
"rank": "4",
"suit": "Clubs",
"card": "4 of Clubs",
"short": "4♣"
},
{
"rank": "Ace",
"suit": "Clubs",
"card": "Ace of Clubs",
"short": "A♣"
},
{
"rank": "7",
"suit": "Diamonds",
"card": "7 of Diamonds",
"short": "7♦"
},
{
"rank": "7",
"suit": "Spades",
"card": "7 of Spades",
"short": "7♠"
},
{
"rank": "5",
"suit": "Diamonds",
"card": "5 of Diamonds",
"short": "5♦"
},
{
"rank": "10",
"suit": "Clubs",
"card": "10 of Clubs",
"short": "10♣"
},
{
"rank": "10",
"suit": "Diamonds",
"card": "10 of Diamonds",
"short": "10♦"
},
{
"rank": "6",
"suit": "Hearts",
"card": "6 of Hearts",
"short": "6♥"
},
{
"rank": "King",
"suit": "Spades",
"card": "King of Spades",
"short": "K♠"
},
{
"rank": "Jack",
"suit": "Spades",
"card": "Jack of Spades",
"short": "J♠"
},
{
"rank": "Ace",
"suit": "Hearts",
"card": "Ace of Hearts",
"short": "A♥"
},
{
"rank": "5",
"suit": "Hearts",
"card": "5 of Hearts",
"short": "5♥"
},
{
"rank": "King",
"suit": "Clubs",
"card": "King of Clubs",
"short": "K♣"
},
{
"rank": "10",
"suit": "Hearts",
"card": "10 of Hearts",
"short": "10♥"
},
{
"rank": "2",
"suit": "Diamonds",
"card": "2 of Diamonds",
"short": "2♦"
},
{
"rank": "Ace",
"suit": "Spades",
"card": "Ace of Spades",
"short": "A♠"
},
{
"rank": "3",
"suit": "Clubs",
"card": "3 of Clubs",
"short": "3♣"
},
{
"rank": "5",
"suit": "Clubs",
"card": "5 of Clubs",
"short": "5♣"
},
{
"rank": "8",
"suit": "Hearts",
"card": "8 of Hearts",
"short": "8♥"
},
{
"rank": "3",
"suit": "Spades",
"card": "3 of Spades",
"short": "3♠"
},
{
"rank": "6",
"suit": "Clubs",
"card": "6 of Clubs",
"short": "6♣"
},
{
"rank": "4",
"suit": "Diamonds",
"card": "4 of Diamonds",
"short": "4♦"
},
{
"rank": "2",
"suit": "Hearts",
"card": "2 of Hearts",
"short": "2♥"
},
{
"rank": "3",
"suit": "Diamonds",
"card": "3 of Diamonds",
"short": "3♦"
},
{
"rank": "9",
"suit": "Diamonds",
"card": "9 of Diamonds",
"short": "9♦"
},
{
"rank": "5",
"suit": "Spades",
"card": "5 of Spades",
"short": "5♠"
},
{
"rank": "3",
"suit": "Hearts",
"card": "3 of Hearts",
"short": "3♥"
},
{
"rank": "6",
"suit": "Diamonds",
"card": "6 of Diamonds",
"short": "6♦"
}
],
"top_card": {
"rank": "8",
"suit": "Spades",
"card": "8 of Spades",
"short": "8♠"
},
"bottom_card": {
"rank": "6",
"suit": "Diamonds",
"card": "6 of Diamonds",
"short": "6♦"
},
"sample_hand": [
{
"rank": "8",
"suit": "Spades",
"card": "8 of Spades",
"short": "8♠"
},
{
"rank": "2",
"suit": "Spades",
"card": "2 of Spades",
"short": "2♠"
},
{
"rank": "Queen",
"suit": "Hearts",
"card": "Queen of Hearts",
"short": "Q♥"
},
{
"rank": "7",
"suit": "Clubs",
"card": "7 of Clubs",
"short": "7♣"
},
{
"rank": "Queen",
"suit": "Spades",
"card": "Queen of Spades",
"short": "Q♠"
}
]
}
}
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 |
|---|---|---|---|
total_cards | number | 52 | Total number of cards in the shuffled deck |
decks_used | number | 1 | Number of decks combined for this shuffle |
includes_jokers | boolean | false | Whether jokers are included in this deck |
shuffle_method | string | "fisher-yates" | Shuffling algorithm used for randomization |
cards | array[52] | Complete shuffled deck with all card details | |
rank | string | "8" | Card rank value like Ace, King, or number |
suit | string | "Spades" | Card suit: Spades, Hearts, Diamonds, or Clubs |
card | string | "8 of Spades" | Full card name like King of Hearts |
short | string | "8♠" | Abbreviated card notation with suit symbols |
top_card | object | {...} | First card in the shuffled deck sequence |
rank | string | "8" | Top card rank value |
suit | string | "Spades" | Top card suit |
card | string | "8 of Spades" | Top card full name |
short | string | "8♠" | Top card abbreviated notation |
bottom_cardPremium | object | {...} | Last card in the shuffled deck sequence |
rankPremium | string | "6" | Bottom card rank value |
suitPremium | string | "Diamonds" | Bottom card suit |
cardPremium | string | "6 of Diamonds" | Bottom card full name |
shortPremium | string | "6♦" | Bottom card abbreviated notation |
sample_handPremium | array[5] | First five cards as example hand from deck | |
rankPremium | string | "8" | Sample hand card rank value |
suitPremium | string | "Spades" | Sample hand card suit |
cardPremium | string | "8 of Spades" | Sample hand card full name |
shortPremium | string | "8♠" | Sample hand card abbreviated notation |
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 — 2 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 | Card Deck Shuffler calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
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.
Call it from cURL — GET /v1/carddeckshuffler
No SDK to install — this is a plain HTTPS call to /v1/carddeckshuffler with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/carddeckshuffler" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
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/carddeckshuffler
Install the Node.js SDK, then call the Card Deck Shuffler API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/carddeckshufflerconst res = await fetch("https://api.apiverve.com/v1/carddeckshuffler", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/carddeckshuffler
Install the Python SDK, then call the Card Deck Shuffler API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-carddeckshufflerimport requests
res = requests.get(
"https://api.apiverve.com/v1/carddeckshuffler",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
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/carddeckshuffler
Install the C# / .NET SDK, then call the Card Deck Shuffler API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.CardDeckShufflerusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/carddeckshuffler");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/carddeckshuffler
No SDK to install — this is a plain HTTPS call to /v1/carddeckshuffler 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/carddeckshuffler", 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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/carddeckshuffler
No SDK to install — this is a plain HTTPS call to /v1/carddeckshuffler with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/carddeckshuffler");
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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/carddeckshuffler
No SDK to install — this is a plain HTTPS call to /v1/carddeckshuffler with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/carddeckshuffler")
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.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Card Deck Shuffler form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Card Deck Shuffler API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Card Deck Shuffler API.
Games
- Acrostic Puzzle Generator
- Anagram Puzzle Generator
- Card Deck Shuffler
- Coin Flipper
- Crossword Generator
- Cryptogram Generator
- Dice Roller
- Fill in the Blanks Generator
- Fortune Cookie Generator
- Game Character Generator
- Hangman Word Generator
- Lottery Number Generator
- Mad Libs Generator
- Maze Generator
- Rock Paper Scissors
- Slot Machine Simulator
- Spelling Bee Generator
- Superhero Name Generator
- Word Ladder Generator
- Word Scramble Generator
- Word Search Generator
Related articles
All articles →
Add Daily Horoscopes to Your App in 5 MinutesBuild a horoscope feature your users will actually check daily. Working code included.Read
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read