> For the complete documentation index, see [llms.txt](https://docs.pullbay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pullbay.com/documentation/api-and-references/services-overview.md).
# Services Overview
Pullbay provides a unified API platform for accessing data from multiple sources. This page outlines all available services, their current status, and the types of endpoints supported across the platform.
## Available Services
### App Store (🟢 Operational)
**iOS app data from the Apple App Store**
Access reviews, ratings, and metadata for iOS applications across 15+ countries. Perfect for competitive analysis, sentiment monitoring, and market research.
* **Data Available**: Reviews, ratings, metadata, helpful votes, version information
* **Countries**: 15+ including US, UK, Germany, France, Japan, Canada, Australia, Brazil, Spain, Italy, South Korea, China, India, Russia, Mexico
* **Update Frequency**: Periodic (typically hours to daily)
* **Endpoints**:
* `GET /v1/app-store/reviews` (standard pagination)
* `GET /v1/app-store/reviews/all` (managed pagination)
**Documentation**: [App Store API Guide](broken://pages/fa26eeb692e7c2843d77b6af7aaa167dbd341f2f)
***
### Google Play (Coming Soon)
**Android app data from Google Play Store**
Android application data including reviews, ratings, and metadata. Currently in development.
* **Status**: Coming soon
* **Data planned**: Reviews, ratings, metadata
***
### Review Platforms (Coming Soon)
**Reviews from Trustpilot, Glassdoor, and other major review platforms**
Consolidate reviews across multiple review platforms with a single API. Monitor your company reputation, employee satisfaction, and customer feedback across platforms.
* **Planned Platforms**: Trustpilot, Glassdoor, and additional platforms
* **Status**: Under development — estimated availability Q4 2026
* **Data Available**: Reviews, ratings, metadata, reviewer profiles
* **Expected Endpoints**:
* `GET /v1/reviews/{platform}/results`
* `GET /v1/reviews/{platform}/all`
***
## Endpoint Types
Pullbay APIs use three primary endpoint types, each serving different use cases:
### Detail Endpoints
Fetch detailed information about a single item.
| Characteristic | Description |
| --------------- | --------------------------------------------- |
| **Purpose** | Retrieve in-depth data for a single resource |
| **Response** | Single object with all available fields |
| **Pagination** | Not applicable |
| **Use Case** | Fetch app metadata, individual review details |
| **Example** | `GET /v1/app-store/app/{app_id}` (planned) |
| **Credit Cost** | 1 credit per request |
***
### List Endpoints
Fetch multiple items with pagination support. Two variants are provided:
#### Standard Pagination (`/reviews`)
You manage pagination manually using cursors.
| Characteristic | Description |
| --------------- | -------------------------------------------------------------- |
| **Purpose** | Retrieve paginated collections with granular control |
| **Response** | Array of objects + pagination metadata |
| **Pagination** | Manual (cursor-based) |
| **Use Case** | Real-time applications, streaming data, UI applications |
| **Example** | `GET /v1/app-store/reviews?app_id=123&limit=50&cursor=...` |
| **Credit Cost** | 1 credit per page (you control pagination) |
| **Best For** | When you need fine-grained control or want to minimize credits |
#### Managed Pagination (`/reviews/all`)
The API handles all pagination internally and returns complete results in a single call.
| Characteristic | Description |
| --------------- | ---------------------------------------------------------- |
| **Purpose** | Retrieve complete datasets with automatic pagination |
| **Response** | Array of all matching objects + metadata |
| **Pagination** | Automatic (handled server-side) |
| **Use Case** | Batch processing, data exports, scheduled jobs, automation |
| **Example** | `GET /v1/app-store/reviews/all?app_id=123` |
| **Credit Cost** | 1 credit per page fetched (varies based on result count) |
| **Best For** | Simplicity and one-time data collection |
***
### Search Endpoints
Search for items using query parameters. Currently in development for Google Search service.
| Characteristic | Description |
| --------------- | -------------------------------------------------------------- |
| **Purpose** | Find items matching specific search criteria |
| **Response** | Array of matching results with relevance scoring |
| **Pagination** | Available for large result sets |
| **Use Case** | Search apps by name, search for keywords, competitor discovery |
| **Example** | `GET /v1/app-store/search?query=productivity` |
| **Credit Cost** | 1 credit per page of results |
***
## Pagination Comparison
### When to Use Standard Pagination
* Building user-facing applications with pagination UI
* Real-time data feeds or dashboards
* Want to minimize credit usage by fetching only needed pages
* Need fine control over request batching
* Handling requests with strict latency requirements
### When to Use Managed Pagination
* Scheduled batch processing jobs
* Data export and archival workflows
* Feeding data into analysis pipelines
* n8n, Make, and other automation tools
* One-time data collection tasks
* Loading data into data warehouses
***
## Understanding Endpoint Documentation
Each Pullbay API endpoint is documented with the following structure:
### Description
Overview of what the endpoint does and when to use it.
### Parameters
Table of all request parameters with:
* Parameter name
* Data type (string, integer, boolean, array)
* Required/optional status
* Default value (if any)
* Description and valid values
### Response Schema
Complete specification of the response object including:
* Field names and types
* Nested object structures
* Possible values and ranges
* Field descriptions
### Examples
* **cURL request** with real data
* **JSON response** showing actual response structure
* **Python/JavaScript/Node.js code** demonstrating integration
### Credit Cost
How many credits each request consumes. Standard pagination lists cost per page. Managed pagination lists cost per page fetched internally.
***
## Service Status
All Pullbay services display their operational status in your dashboard. Status indicators:
| Status | Symbol | Meaning | Impact |
| -------------- | ------ | ------------------------------------------ | ----------------------- |
| Operational | 🟢 | Service fully functional | No impact to operations |
| Degraded | 🟡 | Service operating with reduced performance | Slower response times |
| Partial Outage | 🟠| Service partially unavailable | Some requests may fail |
| Outage | 🔴 | Service unavailable | All requests will fail |
{% stepper %}
{% step %}
### Log in to your Pullbay dashboard
{% endstep %}
{% step %}
### Visit the **Status** section in the main navigation
{% endstep %}
{% step %}
### View current operational status for all services and endpoints
{% endstep %}
{% step %}
### Subscribe to status updates to receive notifications of incidents
{% endstep %}
{% endstepper %}
***
## Requesting New Data Sources
Have a data source you'd like Pullbay to support? We're always adding new services based on customer demand.
**To request a new data source:**
{% stepper %}
{% step %}
### Log in to your Pullbay dashboard
{% endstep %}
{% step %}
### Navigate to **Support → Feature Requests**
{% endstep %}
{% step %}
### Submit your request with details about:
* The data source you need
* Your use case
* Expected data volume and frequency
* Any specific data fields required
{% endstep %}
{% endstepper %}
Our product team reviews all feature requests and prioritizes based on demand and feasibility. Popular requests often get built into the roadmap.
***
## Frequently Asked Questions
When will Google Play be available?
Google Play service is currently under development with an estimated availability in Q3 2026. Follow your dashboard for updates, or subscribe to our email newsletter to receive launch announcements.
Can I request a new data source?
Absolutely! We're constantly adding new services. Visit your Pullbay dashboard and use the Feature Requests section to submit your request. The more customers request a specific data source, the higher priority it receives.
What's the difference between standard and managed endpoints?
**Standard endpoints** (`/reviews`) require you to manage pagination manually with cursors. You control how much data to fetch and when, making this option good for real-time applications and minimizing credit usage.
**Managed endpoints** (`/reviews/all`) automatically handle all pagination internally and return complete results in a single call. This is simpler to integrate but may consume more credits if there are many pages. Best for batch jobs and automation platforms.
Do I get historical data?
Yes. When you fetch reviews, you get all available historical reviews from the platform, not just recent ones. The exact amount of historical data varies by platform and app popularity.
Can I set up alerts when new data is available?
This feature is currently under development. For now, you can set up scheduled API calls using n8n or other automation tools to periodically fetch new reviews and trigger notifications based on review content.
What happens when a service is in Partial Outage?
During a partial outage, some API requests may fail. These typically fail with a 503 (Service Unavailable) status code. We recommend implementing retry logic with exponential backoff in your integrations. Check the Status page for details on which endpoints are affected.
Can I use Pullbay with Zapier, Make, or other automation tools?
Yes! Pullbay works with any automation platform that supports HTTP requests or webhooks. We provide detailed integration guides for popular tools like n8n. Check the [n8n Integration Guide](broken://pages/8dd219ffa1fe8bceebe24f5db78c5943f49c89bb) for examples.
How are credits calculated?
Each API call has an associated credit cost that varies by endpoint type:
* **Standard pagination**: 1 credit per page request
* **Managed pagination**: 1 credit per page fetched internally
* **Search endpoints**: 1-2 credits per search (depending on result count)
Monitor your credit usage in the dashboard. We'll alert you when you're running low.
***
## Next Steps
* [**App Store API Guide**](broken://pages/fa26eeb692e7c2843d77b6af7aaa167dbd341f2f): Complete reference for the currently available App Store service
* [**API Integration Guide**](broken://pages/e3214b83044832a2dc3cb98f53438859f49ba5f8): Learn how to integrate Pullbay into your backend
* [**n8n Integration Guide**](broken://pages/8dd219ffa1fe8bceebe24f5db78c5943f49c89bb): Set up automated workflows with n8n
For questions about upcoming services or to request features, contact our support team through your Pullbay dashboard.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.pullbay.com/documentation/api-and-references/services-overview.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.