Cookie Preferences
We use cookies to personalize content and analyze traffic. See our Cookie Policy.
No output yet. Submit the form to generate content.
Transparent pricing with no hidden fees. Pay as you go.
| Rule & Modality | Channel | Credits | Price (USD) | Official / Reference Price | Daily Savings |
|---|---|---|---|---|---|
audio-space-search otherTwitter | Starter | 0.01per post | $0.00005 | - | - |
Competitor pricing costs $45.450 more
ApiPass is 90.90% lower, estimated at multiple calls returning 10,000 returned posts total
audio-space-search
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Search and discover Twitter (X) Spaces across live, upcoming, and past audio conversations with a single API call.
The Twitter Graphql Audio Space Search API on ApiPass is a managed endpoint that lets developers programmatically search Twitter Spaces — the platform's live audio conversation feature — using flexible keyword queries and status filters. Built on top of Twitter's internal GraphQL layer, this API allows you to retrieve Spaces matching a specific topic, keyword, or state (such as Upcoming, Live, or Past) without needing to scrape the web interface or manage Twitter's authentication complexity. ApiPass wraps the entire workflow into a simple two-step task-based system: submit a search request via POST /api/v1/jobs/createTask, then retrieve structured JSON results via GET /api/v1/jobs/recordInfo. The API is ideal for building audio content discovery tools, social listening dashboards, and real-time monitoring pipelines around Twitter's audio ecosystem.
A consistent create-task / query-task pattern across all ApiPass endpoints makes integration predictable and easy to standardize across your codebase.
The default auto channel automatically allocates requests across starter, regular, and official providers based on real-time pricing and stability metrics, balancing cost and reliability without manual tuning.
Skip the OAuth flow, developer account approval, and rate-limit juggling — just use your ApiPass Bearer token.
Search by keyword (query) and narrow by Space status (filter) such as Upcoming to focus on scheduled sessions relevant to your use case.
Provide an optional callBackUrl to receive automatic notifications when tasks complete, eliminating the need for polling loops in production systems.
Choose the starter tier for ultra-low-cost bulk experimentation or the official tier when you need maximum stability at native API pricing — all through the same interface.
Combine a free-text query with a filter parameter (e.g., Upcoming) to retrieve exactly the Spaces you care about.
Long-running searches are handled asynchronously with a taskId, and task states (waiting, queuing, generating, success, fail) give you full visibility into processing status.
Results are delivered inside a clean resultJson.resultObject payload, ready to be parsed, stored, or piped directly into downstream analytics.
Curated feeds that surface upcoming Spaces around specific topics like crypto, AI, or sports.
Monitor brand mentions and industry conversations happening in live audio, not just tweets.
Help hosts identify trending topics and optimal times to schedule their own Spaces.
Track when competitors or industry leaders launch audio events and analyze participation patterns.
See how ApiPass simplifies access, pricing, and scalability compared to Twitter's official Spaces search endpoint — so you can choose the right fit for your project.
Twitter's official API requires an approved developer account, elevated access tiers, and strict rate limits, and its paid plans can be prohibitively expensive for small teams. ApiPass exposes the same functionality via a simple Bearer-token request with no application process, letting you start building in minutes.
Twitter's official API offers a single fixed pricing structure per access tier. ApiPass lets you dynamically choose between starter, regular, and official providers — or default to auto — so you can scale cost and reliability independently based on the workload.
Aggregate keyword-based Space searches to detect emerging conversation topics before they hit mainstream feeds.
Track all Spaces around a conference hashtag, product launch, or crisis event in real time.
Journalists and researchers can discover live audio discussions relevant to ongoing stories.
Measure how often a brand or campaign keyword appears in Twitter's audio ecosystem alongside traditional tweet-based mentions.
Sign up on ApiPass and generate an API key from your dashboard. You'll use it as a Bearer token in the Authorization header for every request.
Send a POST request to /api/v1/jobs/createTask with the model set to twitter/graphql/audio-space-search. Provide your search parameters inside input.variables, including a query keyword and an optional filter such as Upcoming to narrow down results. You can also include an optional callBackUrl to receive automatic notifications when the task completes. The response will return a unique taskId that you'll use to retrieve results.
Send a GET request to /api/v1/jobs/recordInfo with your taskId as a query parameter. Monitor the state field — once it returns success, your Space search results will be available inside data.resultJson.resultObject, ready to parse and integrate into your application. If you provided a callBackUrl in Step 2, ApiPass will push the results to your endpoint automatically, so no polling is needed.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Search Twitter Spaces
The API accepts a JSON payload with the following structure:
1{
2 "model": "string",
3 "callBackUrl": "string (optional)",
4 "channel": "auto",
5 "input": {
6 "variables": {
7 "filter": "string",
8 "query": "string"
9 }
10 }
11}modelRequiredstringThe model name to use for generation
"twitter/graphql/audio-space-search"
callBackUrlOptionalstringCallback URL for task completion notifications. If omitted, no callback will be sent.
"https://your-domain.com/api/callback"
channelOptionalstringYou may specify the corresponding provider within APIPASS via the channel parameter; these providers handle the actual image and video generation tasks. APIPASS currently offers three provider options:
The default value for the channel parameter is auto. When enabled, APIPASS automatically allocates tasks across available providers based on real-time pricing and stability metrics to balance minimal cost and reliable performance. Retain the default auto value unless you have custom routing requirements.
Available options:
auto
The input object contains the following parameters:
input.variables.filterOptionalstringUpcoming
input.variables.queryOptionalstringa
1curl -X POST "https://api.apipass.dev/api/v1/jobs/createTask" \
2 -H "Content-Type: application/json" \
3 -H "Authorization: Bearer YOUR_API_KEY" \
4 -d '{
5 "model": "twitter/graphql/user-by-screen-name",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "variables": {
9 "filter": "Upcoming",
10 "query": "a"
11 }
12 }
13 }'1{
2 "code": 200,
3 "message": "success",
4 "data": {
5 "taskId": "task_12345678"
6 }
7}codeStatus code, 200 for success, others for failure
messageResponse message, error description when failed
data.taskIdTask ID for querying task status and results
