Mock sample for your project: RAWG Video Games Database API

Integrate with "RAWG Video Games Database API" from rawg.io in no time with Mockoon's ready to use mock sample

RAWG Video Games Database API

rawg.io

Version: v1.0

Use this API in your project

Open in the application
Download mock API file
đź“– How to use?
Own this API? Add a Mockoon button on your website.

Start working with "RAWG Video Games Database API" right away by using this ready-to-use mock sample. API mocking can greatly speed up your application development by removing all the tedious tasks or issues: API key provisioning, account creation, unplanned downtime, etc.
It also helps reduce your dependency on third-party APIs and improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.

Description

The largest open video games database.
Why build on RAWG
More than 350,000 games for 50 platforms including mobiles.
Rich metadata: tags, genres, developers, publishers, individual creators, official websites, release dates,
Metacritic ratings.
Where to buy: links to digital distribution services
Similar games based on visual similarity.
Player activity data: Steam average playtime and RAWG player counts and ratings.
Actively developing and constantly getting better by user contribution and our algorithms.
Terms of Use
Free for personal use as long as you attribute RAWG as the source of the data and/or images and add an active
hyperlink from every page where the data of RAWG is used.
Free for commercial use for startups and hobby projects with not more than 100,000 monthly active users or 500,000
page views per month. If your project is larger than that, email us at [email protected] for
commercial terms.
No cloning. It would not be cool if you used our API to launch a clone of RAWG. We know it is not always easy
to say what is a duplicate and what isn't. Drop us a line at [email protected] if you are in doubt,
and we will talk it through.
You must include an API key with every request. The key can be obtained at https://rawg.io/apidocs.
If you don’t provide it, we may ban your requests.
Read more.

Other APIs in the same category

NPR Listening Service

npr.org
Audio recommendations tailored to a user's preferences
Use API

MLB v3 Scores

sportsdata.io
MLB scores API.
Use API

NPR Authorization Service

npr.org
The interface to our OAuth2 server
Use API

MLB v3 RotoBaller Articles

sportsdata.io
Use API

NBA v3 Stats

sportsdata.io
Use API

Vimeo

vimeo.com
Use API

NHL v3 Stats

sportsdata.io
Use API

SportsData API

whapi.com
The William Hill SportsData REST API is a collection of GET methods to provide William Hill product data such as sport, competition, event, market and selection data (including prices).
Use API

MLB v3 Play-by-Play

sportsdata.io
MLB play-by-play API.
Use API

NBA v3 Scores

sportsdata.io
Use API

LoL v3 Scores

sportsdata.io
LoL v3 Scores
Use API

Sessions API

whapi.com
The William Hill Sessions API uses a central authentication service (CAS*) on all resources that require access to a customer’s account or betting functionality. To authenticate, you’ll need to supply a sportsbook username and password, in return you will be given an authentication ticket, which you can use on the majority of requests found within our services. The Sessions API should be used whenever you want to login a customer and: continue to use the William Hill API for that customer’s transactions use other CAS-enabled William Hill services outside the suite of APIs CAS is an enterprise Single Sign-On solution for web services (see https://wiki.jasig.org/display/CAS/Home). It is used by many William Hill services. Note: all requests must be executed over HTTPS and include an API key and secret. Authentication Ticket Expiration Times When a customer is logged in using the Sessions API, they are given an Authentication Ticket; using this ticket on subsequent API requests gives you access to account activities (such as placing a bet, deposits, etc). However, this ticket is only valid for a given period of time depending on how it is used. If the ticket is used and then has a period of inactivity longer than 7,200 seconds (2 hours), then the ticket will expire and further requests using the ticket will be denied - in effect, a customer has been logged out and will need to authenticate again. Normally, any ticket issued only has a maximum life expectancy of 28,000 seconds (8 hours) after which it can no longer be used, even if it has been used regularly. The customer again will be effectively logged out and will need to authenticate again. If you wish to avoid this, you need to set the query parameter extended to Y, which will enable your application to generate a ticket valid for 60 days without expiring due to inactivity.
Use API
⬅ Back to the list of mock samples