Pricing is based on combination of montly cost and cost per "API unit". Different methods require a different amount of units. The Unit Cost Summary table farther down this page shows the costs for each method.
Plan Name | Monthly Cost | Usage Cost | Rate Limit | Description |
---|---|---|---|---|
Enterprise |
|
Best for
|
To begin using the Adbeat API, please contact [email protected]
Method Name | Request Cost | Result Cost |
---|---|---|
Ad Methods | ||
adMetrics | 100 units | 5 units/row ** |
adTerms | 25 units | 1 unit/row |
Advertiser Methods | ||
advertiserMetrics | 100 units | 5 units/row ** |
advertiserInfo | 250 units | --- |
advertiserEvents | 100 units | 5 units/row |
advertisers | 25 units | 1 unit/row |
campaignMetrics | 100 units | 5 units/row ** |
campaigns | 25 units | 1 unit/row |
categories | 25 units | 1 unit/row |
Publisher Methods | ||
publisherInfo | 250 units | --- |
publishers | 25 units | 1 unit/row |
Helper Methods | ||
adSizes | 1 unit | --- |
adTypes | 1 unit | --- |
eventTypes | 1 unit | --- |
countries | 1 unit | --- |
networks | 1 unit | --- |
platforms | 1 unit | --- |
** These methods may incur additional unit costs depending on which parameters you pass. See individual method documentation for details.
All responses include the apiUnits
field which returns the number of API units consumed by the request. (See Response Format.)
To help you better understand how unit costs are calculated, let's look at an example:
If we'd like to use the adTerms method we can see that the Unit Cost Summary table tells us it has a Request Cost of 25 units and a Result Cost of 1 unit/row.
Now let's make our API call:
http://api.adbeat.com/v3/{api-key}/adTerms/?q=insurance
Since we didn't specify how many rows to return, the adTerms method will return the default 10 rows. The data it returns will look something like this:
{ "statusCode": 200, "numHits": 19880, "hits": [{ "countryId": "us", "score": 142745, "suggestion": "insurance", "platformId": "desktop" }, { "countryId": "us", "score": 26023, "suggestion": "insurance", "platformId": "ipad" }, { "countryId": "us", "score": 25995, "suggestion": "insurance", "platformId": "android" }, { "countryId": "us", "score": 22183, "suggestion": "insurance", "platformId": "iphone" }, { "countryId": "gb", "score": 20406, "suggestion": "insurance", "platformId": "desktop" }, { "countryId": "us", "score": 19150, "suggestion": "insurance", "platformId": "androidtablet" }, { "countryId": "us", "score": 12717, "suggestion": "car insurance", "platformId": "desktop" }, { "countryId": "ca", "score": 10818, "suggestion": "insurance", "platformId": "desktop" }, { "countryId": "au", "score": 7721, "suggestion": "insurance", "platformId": "desktop" }, { "countryId": "us", "score": 5758, "suggestion": "auto insurance", "platformId": "desktop" }], "apiUnits": 35, "statusMsg": "successful adTerms request", "requestParameters": { "q": "insurance" }, "handler": "adTerms" }
In the above data, each item in the "hits" array is the equivalent of 1 row.
So how many units did our API call cost us? Let's break it down:
API Call http://api.adbeat.com/v3/{api-key}/adTerms/?q=insurance |
Cost |
---|---|
Request Cost | 25 units |
Result Cost (1 unit x 10 rows) | 10 units |
Total Unit Cost | 35 units |
Keep in mind that many methods support a &rows
parameter. Using this parameter you can specify the exact number of rows you'd like returned. Therefore, we can modify the example API call above to limit it to return just 5 rows like this:
http://api.adbeat.com/v3/{api-key}/adTerms/?q=insurance&rows=5
In this case, the costs would change like so:
API Call http://api.adbeat.com/v3/{api-key}/adTerms/?q=insurance&rows=5 |
Cost |
---|---|
Request Cost | 25 units |
Result Cost (1 unit x 5 rows) | 5 units |
Total Unit Cost | 30 units |