Rock Paper Scissors API
Overview
To use Rock Paper Scissors, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/rockpaperscissorsExample
How to call the Rock Paper Scissors API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/rockpaperscissors?choice=rock&rounds=5" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/rockpaperscissors?choice=rock&rounds=5', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/rockpaperscissors?choice=rock&rounds=5', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/rockpaperscissors?choice=rock&rounds=5", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"total_rounds": 5,
"player_choice_mode": "manual",
"games": [
{
"round": 1,
"player_choice": "rock",
"player_emoji": "🪨",
"computer_choice": "paper",
"computer_emoji": "📄",
"outcome": "computer",
"message": "Computer wins! undefined"
},
{
"round": 2,
"player_choice": "rock",
"player_emoji": "🪨",
"computer_choice": "rock",
"computer_emoji": "🪨",
"outcome": "tie",
"message": "It's a tie! Both chose rock"
},
{
"round": 3,
"player_choice": "rock",
"player_emoji": "🪨",
"computer_choice": "rock",
"computer_emoji": "🪨",
"outcome": "tie",
"message": "It's a tie! Both chose rock"
},
{
"round": 4,
"player_choice": "rock",
"player_emoji": "🪨",
"computer_choice": "paper",
"computer_emoji": "📄",
"outcome": "computer",
"message": "Computer wins! undefined"
},
{
"round": 5,
"player_choice": "rock",
"player_emoji": "🪨",
"computer_choice": "scissors",
"computer_emoji": "✂️",
"outcome": "player",
"message": "You win! Rock crushes scissors"
}
],
"results": {
"player_wins": 1,
"computer_wins": 2,
"ties": 2,
"player_win_percentage": 20,
"computer_win_percentage": 40,
"tie_percentage": 40
},
"overall_winner": "computer",
"game_rules": {
"rock_beats": "scissors",
"paper_beats": "rock",
"scissors_beats": "paper"
}
}
}Authentication
The Rock Paper Scissors API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Rock Paper Scissors API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Rock Paper Scissors API:
Play Rock Paper Scissors
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
choice | string | optional | Your choice - omit for random Supported values: rockpaperscissorsrp | ||
rounds | integer | optional | Number of rounds to play Range: 1 - 100 |
Response
The Rock Paper Scissors API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<total_rounds>5</total_rounds>
<player_choice_mode>manual</player_choice_mode>
<games>
<game>
<round>1</round>
<player_choice>rock</player_choice>
<player_emoji>🪨</player_emoji>
<computer_choice>paper</computer_choice>
<computer_emoji>📄</computer_emoji>
<outcome>computer</outcome>
<message>Computer wins! undefined</message>
</game>
<game>
<round>2</round>
<player_choice>rock</player_choice>
<player_emoji>🪨</player_emoji>
<computer_choice>rock</computer_choice>
<computer_emoji>🪨</computer_emoji>
<outcome>tie</outcome>
<message>It's a tie! Both chose rock</message>
</game>
<game>
<round>3</round>
<player_choice>rock</player_choice>
<player_emoji>🪨</player_emoji>
<computer_choice>rock</computer_choice>
<computer_emoji>🪨</computer_emoji>
<outcome>tie</outcome>
<message>It's a tie! Both chose rock</message>
</game>
<game>
<round>4</round>
<player_choice>rock</player_choice>
<player_emoji>🪨</player_emoji>
<computer_choice>paper</computer_choice>
<computer_emoji>📄</computer_emoji>
<outcome>computer</outcome>
<message>Computer wins! undefined</message>
</game>
<game>
<round>5</round>
<player_choice>rock</player_choice>
<player_emoji>🪨</player_emoji>
<computer_choice>scissors</computer_choice>
<computer_emoji>✂️</computer_emoji>
<outcome>player</outcome>
<message>You win! Rock crushes scissors</message>
</game>
</games>
<results>
<player_wins>1</player_wins>
<computer_wins>2</computer_wins>
<ties>2</ties>
<player_win_percentage>20</player_win_percentage>
<computer_win_percentage>40</computer_win_percentage>
<tie_percentage>40</tie_percentage>
</results>
<overall_winner>computer</overall_winner>
<game_rules>
<rock_beats>scissors</rock_beats>
<paper_beats>rock</paper_beats>
<scissors_beats>paper</scissors_beats>
</game_rules>
</data>
</response>
status: ok
error: null
data:
total_rounds: 5
player_choice_mode: manual
games:
- round: 1
player_choice: rock
player_emoji: 🪨
computer_choice: paper
computer_emoji: 📄
outcome: computer
message: Computer wins! undefined
- round: 2
player_choice: rock
player_emoji: 🪨
computer_choice: rock
computer_emoji: 🪨
outcome: tie
message: It's a tie! Both chose rock
- round: 3
player_choice: rock
player_emoji: 🪨
computer_choice: rock
computer_emoji: 🪨
outcome: tie
message: It's a tie! Both chose rock
- round: 4
player_choice: rock
player_emoji: 🪨
computer_choice: paper
computer_emoji: 📄
outcome: computer
message: Computer wins! undefined
- round: 5
player_choice: rock
player_emoji: 🪨
computer_choice: scissors
computer_emoji: ✂️
outcome: player
message: You win! Rock crushes scissors
results:
player_wins: 1
computer_wins: 2
ties: 2
player_win_percentage: 20
computer_win_percentage: 40
tie_percentage: 40
overall_winner: computer
game_rules:
rock_beats: scissors
paper_beats: rock
scissors_beats: paper
| key | value |
|---|---|
| total_rounds | 5 |
| player_choice_mode | manual |
| games | [{round:1,player_choice:rock,player_emoji:🪨,computer_choice:paper,computer_emoji:📄,outcome:computer,message:Computer wins! undefined},{round:2,player_choice:rock,player_emoji:🪨,computer_choice:rock,computer_emoji:🪨,outcome:tie,message:It's a tie! Both chose rock},{round:3,player_choice:rock,player_emoji:🪨,computer_choice:rock,computer_emoji:🪨,outcome:tie,message:It's a tie! Both chose rock},{round:4,player_choice:rock,player_emoji:🪨,computer_choice:paper,computer_emoji:📄,outcome:computer,message:Computer wins! undefined},{round:5,player_choice:rock,player_emoji:🪨,computer_choice:scissors,computer_emoji:✂️,outcome:player,message:You win! Rock crushes scissors}] |
| results | {player_wins:1,computer_wins:2,ties:2,player_win_percentage:20,computer_win_percentage:40,tie_percentage:40} |
| overall_winner | computer |
| game_rules | {rock_beats:scissors,paper_beats:rock,scissors_beats:paper} |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
total_rounds | number | Total number of rounds played in the game | |
player_choice_mode | string | Mode of player selection: manual or random choice | |
| [ ] Array items: | array[5] | Array of individual game rounds with details | |
└ round | number | Sequential round number in the game series | |
└ player_choice | string | Player's hand choice: rock, paper, or scissors | |
└ player_emoji | string | Emoji representation of player's choice | |
└ computer_choice | string | Computer's hand choice: rock, paper, or scissors | |
└ computer_emoji | string | Emoji representation of computer's choice | |
└ outcome | string | Round outcome: player, computer, or tie result | |
└ messagePremium | string | Human-readable message describing round outcome | |
results | object | Statistical summary of all game rounds played | |
└ player_winsPremium | number | Count of rounds won by the player | |
└ computer_winsPremium | number | Count of rounds won by the computer | |
└ tiesPremium | number | Count of rounds resulting in a tie | |
└ player_win_percentagePremium | number | Percentage of rounds won by player | |
└ computer_win_percentagePremium | number | Percentage of rounds won by computer | |
└ tie_percentagePremium | number | Percentage of rounds resulting in tie | |
overall_winnerPremium | string | Overall game winner: player, computer, or tie | |
game_rules | object | Object defining what each choice beats | |
└ rock_beats | string | What rock beats in the game |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Rock Paper Scissors through GraphQL to combine it with other API calls in a single request. Query only the rock paper scissors data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
rockpaperscissors(
input: {
choice: "rock"
rounds: 5
}
) {
total_rounds
player_choice_mode
games
results {
player_wins
computer_wins
ties
player_win_percentage
computer_win_percentage
tie_percentage
}
overall_winner
game_rules {
rock_beats
paper_beats
scissors_beats
}
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Rock Paper Scissors API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Rock Paper Scissors requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Rock Paper Scissors API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Rock Paper Scissors
Official Rock Paper Scissors packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Rock Paper Scissors works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Rock Paper Scissors?
How many credits does Rock Paper Scissors cost?
Each successful Rock Paper Scissors API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful rock paper scissors lookups.
Can I use Rock Paper Scissors in production?
The free plan is for testing and development only. For production use of Rock Paper Scissors, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Rock Paper Scissors from a browser?
What happens if I exceed my Rock Paper Scissors credit limit?
When you reach your monthly credit limit, Rock Paper Scissors API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








