Mock sample for your project: Hubhopper Partner Integration API(s) - Production

Integrate with "Hubhopper Partner Integration API(s) - Production" from hubhopper.com in no time with Mockoon's ready to use mock sample

Hubhopper Partner Integration API(s) - Production

hubhopper.com

Version: v5

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 "Hubhopper Partner Integration API(s) - Production" 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

This is an interactive document explaining the API(s) that could be used to fetch data from Hubhopper. Use the api key provided to authorize x-api-key and test the API(s). The output data models are also available for reference.

Other APIs in the same category

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

Metadata

haloapi.com

API that provides Metadata information.

Use API

NPR Identity Service

npr.org

The entry point to user-specific information

Use API

EVEMarketer Marketstat API

evemarketer.com

EVEMarketer Marketstat API is almost compatible with EVE-Central's Marketstat API.

Use API

NBA v3 Stats

sportsdata.io

Use API

NBA v3 RotoBaller Premium News

sportsdata.io

Use API

NFL v3 Scores

sportsdata.io

NFL schedules, scores, odds, weather, and news API.

Use API

Accounts API

whapi.com

The Accounts API is a collection of methods used to query a customer account. It allows the developer to retrieve account-related data such as the user account balance. It should be noted that regional variations may exist - so some fields may not be returned for certain territories.

Use API