The data feeds
Enterprise pages can pull their RankRack numbers and reviews as JSON and build any display they like on their own site. This page shows the two feeds, their exact response shapes, and a few of the displays that can be built from them. The data is invented: Example Hosting is not a real company, so the links in the samples lead nowhere.
The provider feed
One request, the page's numbers: name, average, review count, Trust Score and the page URL. Open to cross-origin requests and cached for five minutes.
https://rank-rack.com/embed/example-hosting.json{
"provider": {
"name": "Example Hosting",
"slug": "example-hosting",
"average": 4.3,
"reviewCount": 26,
"trustScore": 78,
"pageUrl": "https://rank-rack.com/provider/example-hosting"
}
}Until a page has reviews, average and trustScore are null rather than numbers:
{
"provider": {
"name": "Example Hosting",
"slug": "example-hosting",
"average": null,
"reviewCount": 0,
"trustScore": null,
"pageUrl": "https://rank-rack.com/provider/example-hosting"
}
}The reviews feed
The same provider block with up to five published reviews under it. Add ?count=1 to ?count=5 to size it; three is the default. Each request draws its own random sample from all of the page's published reviews, and which ones appear is not configurable.
https://rank-rack.com/embed/example-hosting-reviews.json?count=1{
"provider": {
"name": "Example Hosting",
"slug": "example-hosting",
"average": 4.3,
"reviewCount": 26,
"trustScore": 78,
"pageUrl": "https://rank-rack.com/provider/example-hosting"
},
"reviews": [
{
"author": "Dana K.",
"country": "United Kingdom",
"rating": 5,
"title": "Moved three game servers over in one evening",
"body": "The migration help was the reason I picked them. I sent the files over on a Friday, everything was running by Saturday morning, and the one config problem I hit was answered in under an hour. Three months in and I have not had an outage long enough to notice.",
"date": "2026-07-28",
"verification": "verified-purchase",
"invited": true,
"imported": false,
"importedFrom": null,
"editedAt": null
}
]
}Ways you can style it
The display is yours: markup, styling and layout are all up to you. Everything below is built from the feed responses above. However you present the figures, they have to stay accurate - the star rating always appears with its review count.
The migration help was the reason I picked them. I sent the files over on a Friday, everything was running by Saturday morning, and the one config problem I hit was answered in under an hour. Three months in and I have not had an outage long enough to notice.
Performance has been exactly what the spec sheet promised and the panel is easy to work with. My only complaint is that weekend tickets take most of a day to get a first reply. Weekday support is quick.
The server itself has been fine for the year I have had it. The price at renewal was noticeably higher than the price I signed up at, and I only found out from the invoice. Worth keeping, but read the renewal terms before you commit.
"The migration help was the reason I picked them. I sent the files over on a Friday, everything was running by Saturday morning, and the one config problem I hit was answered in under an hour. Three months in and I have not had an outage long enough to notice."
Getting access
The feeds come with Enterprise; plans are on the pricing page. Your page's own URLs are in the client portal under API access once your page is set up.