Dashboard Order Developer FAQ
Login

 Introduction

 API call structure
 Scrape Google Search
 Scraping Bing Search
 Keyword rank tracker


 Source Code download

Basic API information

Minimal API link: https://scraping.services/api?user=_USER@ACCOUNT_&credentials=_CREDENTIALS_
API login: _USER@ACCOUNT_
API key: _CREDENTIALS_

General

Our Dashboard makes scraping as easy as writing an email but often customers want to power their startup or service by our scraping capability full automated.

Our API was designed to allow a hassle-free implementation, developers can easily integrate our API into their projects.
As the API is HTTP(s) based, you can easily test API calls using a web-browser, curl or any other HTTP interface.
It's recommended to take a look at our free code demonstrations.

 

Cost
Each API request comes at the small cost of 0.01 Credits.

That means 100 API requests cost between 0.14 USD to 0.09 USD depending on your current license.



Each API call contains a number of parameters as well as one optional json encoded object.
The API responds with JSON data that can easily be parsed in almost any language.
Any supplied text is expected to be UTF8 encoded and any responses are UTF8 encoded.

 

The API request
Let's start by taking a look at a simple request:

https://scraping.services/api?user=_USER@ACCOUNT_&credentials=_CREDENTIALS_&job_type=info&task=license_info&type=json
The URI is "https://scraping.services/api" with a set of essential parameters:
  • user: your registered email address
  • credentials: your encrypted api key
  • job_type: A job contains a subset of possible tasks, in our example "info"
  • task: The task related to the selected job, in our example "license_info"
  • type: The return format. 'html' and 'json' are available, more types will be available in the future.

The API will respond with the currently active license packed as a json format:

{
  "exceptions": [],
"answer":
{
"license":
{
"id": 1,
"name": "1xsmall",
"monthly_cost": "14.00",
"monthly_credits": "100",
"time_left": "386:31:46",
"time_left_grace": "482:31:46"
}
}
}


The URI always contains the mentioned basic variables for authentication and task/call selection.
Some API calls require more complicated structures to be passed, for example keyword arrays.

In these cases the additional variables are supplied as JSON object encoded POST (or GET) parameter. ("json={....}")
It is up to the programmer to use the "json" parameter or supply the data as single parameters through the URI.


It is recommended to take a look at our free source code and the detailed API documentation.

 

The API response
The API response always contains two json objects: 'exceptions' and 'answer'.

  • exceptions: Empty if no exceptions happened, for example invalid user credentials
  • answer: The actual API response, in our example details about the currently active license

The API response can easily be parsed by almost any programming language.
  • PHP: $array = json_decode($response)
  • Java: JSONObject jsonObject = new JSONObject(response);
  • JavaScript: var obj = JSON.parse(response);
  • C# and .NET: dynamic obj = JsonConvert.DeserializeObject(response);
  • Python: json.load(response)