Rock Paper Scissors API
Rock Paper Scissors API simulates the classic hand game with detailed outcome analysis, statistics, and support for multiple rounds.
The Rock Paper Scissors API provides reliable and fast access to rock paper scissors data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
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/rockpaperscissorsCode Examples
Here are examples of 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)const https = require('https');
const url = require('url');
const options = {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
};
const req = https.request('https://api.apiverve.com/v1/rockpaperscissors?choice=rock&rounds=5', options, (res) => {
let data = '';
res.on('data', (chunk) => data += chunk);
res.on('end', () => console.log(JSON.parse(data)));
});
req.end();<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/rockpaperscissors?choice=rock&rounds=5');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-Key: your_api_key_here',
'Content-Type: application/json'
]);
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($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))
}require 'net/http'
require 'json'
uri = URI('https://api.apiverve.com/v1/rockpaperscissors?choice=rock&rounds=5')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'
response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
class Program
{
static async Task Main(string[] args)
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");
var response = await client.GetAsync("https://api.apiverve.com/v1/rockpaperscissors?choice=rock&rounds=5");
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}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:
Example Responses
{
"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"
}
}
}<?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
Required and optional headers for Rock Paper Scissors API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
X-API-Key | required | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
Accept | optional | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
User-Agent | optional | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
X-Request-ID | optional | req_123456789 | Custom request identifier for tracking and debugging requests |
Cache-Control | optional | no-cache | Control caching behavior for the request and response |
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 supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Rock Paper Scissors directly from browser-based applications without proxy servers.
| CORS Header | Value | Description |
|---|---|---|
Access-Control-Allow-Origin | * | Accepts requests from any origin |
Access-Control-Allow-Methods | * | Accepts any HTTP method |
Access-Control-Allow-Headers | * | Accepts any request headers |
Browser Usage: You can call Rock Paper Scissors directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
Rock Paper Scissors API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all Rock Paper Scissors users.
| Plan | Rate Limit | Description |
|---|---|---|
| Free | 5 requests/min | Hard rate limit enforced - exceeding will return 429 errors |
| Starter | No Limit | Production ready - standard traffic priority |
| Pro | No Limit | Production ready - preferred traffic priority |
| Mega | No Limit | Production ready - highest traffic priority |
Learn more about rate limiting →
Rate Limit Headers
When rate limits apply, each Rock Paper Scissors response includes headers to help you track your usage:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed per time window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Handling Rate Limits
Free Plan: When you exceed your rate limit, Rock Paper Scissors returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.
Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.
Best Practices for Rock Paper Scissors:
- Monitor the rate limit headers to track your Rock Paper Scissors usage (Free plan only)
- Cache rock paper scissors responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle Rock Paper Scissors performance
Note: Rock Paper Scissors rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using Rock Paper Scissors on Free tier.
Error Codes
The Rock Paper Scissors API uses standard HTTP status codes to indicate success or failure:
| Code | Message | Description | Solution |
|---|---|---|---|
200 | OK | Request successful, data returned | No action needed - request was successful |
400 | Bad Request | Invalid request parameters or malformed request | Check required parameters and ensure values match expected formats |
401 | Unauthorized | Missing or invalid API key | Include x-api-key header with valid API key from dashboard |
403 | Forbidden | API key lacks permission or insufficient credits | Check credit balance in dashboard or upgrade plan |
429 | Too Many Requests | Rate limit exceeded (Free: 5 req/min) | Implement request throttling or upgrade to paid plan |
500 | Internal Server Error | Server error occurred | Retry request after a few seconds, contact support if persists |
503 | Service Unavailable | API temporarily unavailable | Wait and retry, check status page for maintenance updates |
Learn more about error handling →
Need help? Contact support with your X-Request-ID for assistance.
Integrate Rock Paper Scissors with SDKs
Get started quickly with official Rock Paper Scissors SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.
Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.
Integrate Rock Paper Scissors with No-Code API Tools
Connect the Rock Paper Scissors API to your favorite automation platform without writing code. Build workflows that leverage rock paper scissors data across thousands of apps.





All platforms use your same API key to access Rock Paper Scissors. Visit our integrations hub for step-by-step 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.



