SignalCoverage and roadmap
We track 205 reference targets across 38 categories. Current status: 92 implemented, 0 experimental, and 113 planned. Evidence: 35 live checked, 0 live unverified, 57 local checks only, and 113 not implemented. Planned targets are not available APIs. A live check is for the exact catalog path; a native route check does not verify a separate compatibility response mapping. Capability mappings do not imply identical options, fields, or reliability.
How to read coverage
Implemented: a related SignalShelf capability exists. Experimental: an extraction path exists but has availability or capability gaps. Planned: no engine is implemented. Live checked: a dated request to a public source succeeded for a specific query and region; this does not guarantee uptime, completeness, parity, or production authorization. Live unverified: a live attempt did not prove extraction worked. Local checks only: app behavior was tested with local fixtures, without recorded live-source evidence for that operation. Not implemented: no SignalShelf route exists. Production blocked by default: live production requests are refused unless the source-specific authorization flag is enabled. Not blocked by a source gate does not mean the whole product is production-ready. /api/v1/coverage contains the full inventory; /api/v1/capabilities lists callable routes.
The aggregate reference OpenAPI lists 199 operations. Endpoint-specific OpenAPI files document 6 additional operations omitted from that aggregate. The LLM index links 9 additional documentation pages, all reconciled to documented operations; 0 linked pages still lack a method/path contract. We build independent extraction engines and use official public APIs where available.
TikTok
| Field | Type | Description |
|---|---|---|
Profile | implemented · local checks only · production blocked by default | GET /v1/tiktok/profile (catalog path). GET /v1/tiktok/profile. Partial owner-consented mapping through TikTok Login Kit and the official Display API. Reads only the TikTok account connected to the authenticated SignalShelf user; a supplied handle must match that account, and arbitrary user_id lookup is rejected. Requests `user.info.basic` fields when granted, adds profile fields only with `user.info.profile`, and follower/following/likes/video counts only with `user.info.stats`; missing or ungranted fields are omitted. Profile cache keys include the granted profile scopes, and OAuth reconnection clears prior TikTok cache entries so data from broader or older account consent is not reused. Postman simulation checks passed, including a basic-only reconnect after broader consent; no TikTok app credentials or live request were used. The prior public-page reader was removed from this reference route after direct and proxy attempts failed; its old live-unverified evidence does not describe this new implementation. App approval and written paid-use clearance remain required, so production stays blocked. Sources: https://developers.tiktok.com/docs/en/display-api-overview, https://developers.tiktok.com/docs/en/tiktok-api-v2-get-user-info, and https://developers.tiktok.com/docs/en/tiktok-api-scopes. |
Profile Region | implemented · local checks only · production blocked by default | GET /v1/tiktok/profile/region (catalog path). GET /api/v1/tiktok-shop/profile-region. Owner-authorized partial mapping to TikTok Shop Affiliate Creator Get Creator Profile. The route verifies that the requested handle matches the exact TikTok Shop account connected by this SignalShelf user, then returns only the official profile `register_region`; it does not substitute `selection_region`, which describes Shop selection eligibility, and does not look up arbitrary public handles. The profile URL is generated from the verified username and is labeled as such. The route is covered only by local HTTP fixtures; no approved app credentials or live provider calls are configured. Affiliate API activation, creator authorization/app review, exact live field validation, and written paid-use/retention clearance remain required, so production is blocked by default. Sources: https://partner.tiktokshop.com/docv2/page/affiliate-integration and https://partner.tiktokshop.com/docv2/page/creator-authorization-guide. |
User's Audience Demographics | planned · not implemented · source review required | Not implemented; rechecked against official TikTok docs on 2026-11-03. TikTok Research Tools explicitly exclude creators, advertisers, and commercial users; they are limited to approved research. TikTok Display API exposes the consenting account’s basic profile and public statistics, not follower audience demographics by arbitrary handle. TikTok Shop seller Marketplace Creator APIs provide a distinct alternative: `GET /affiliate_seller/202406/marketplace_creators/{creator_user_id}` returns Marketplace data groups including `FOLLOWER_INFORMATION` for eligible creators over the last 30 days, and `POST /affiliate_seller/202608/marketplace_creators/search` supports keyword and follower-demographic filters. Both are seller-authorized (`user_type=0`), require `seller.creator_marketplace.read` and a shop cipher, and operate within that seller’s Creator Marketplace; they do not establish unrestricted public handle lookup or paid redistribution permission. Do not substitute seller analytics or infer demographics from public profiles. Revisit only with a documented source matching this public contract and written use/retention rights; alternatively design a separately named seller-authorized feature. Sources: https://developers.tiktok.com/products/research-api/, https://developers.tiktok.com/docs/en/research-api-faq, https://developers.tiktok.com/products/display-api/, https://partner.tiktokshop.com/docv2/page/get-marketplace-creator-performance-202406, and https://partner.tiktokshop.com/docv2/page/search-creators-in-creator-marketplace-202608. |
Collection Videos | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Profile Videos | implemented · local checks only · production blocked by default | GET /v3/tiktok/profile/videos (catalog path). GET /v3/tiktok/profile/videos. Partial owner-consented compatibility route over TikTok Login Kit and the official Display API. The requested handle must match the same SignalShelf user's connected account. Local Postman simulation checks only; no TikTok app credentials or live request. App approval and written paid-use clearance are required before production. Partial owner-consented mapping: only the TikTok account connected to the authenticated SignalShelf user is available, and its handle is checked before a fresh video-list request. The official source does not provide arbitrary profile lookup, region selection, popularity sorting, pinned-post control, or the vendor response schema. App approval and written paid-use clearance are still required. |
Video Info | implemented · local checks only · production blocked by default | GET /v2/tiktok/video (catalog path). GET /v2/tiktok/video. Partial owner-consented mapping through TikTok Login Kit and official Display API Query Videos. Accepts canonical video URLs only when the username matches this SignalShelf user’s connected account; TikTok also verifies the video ID belongs to that authorized user. Returns only source-backed video metadata. Arbitrary creators, transcripts, region routing, and media downloads are unsupported. Local simulation only; no TikTok credentials or live request. App approval and written commercial-use clearance remain required; production is source-gated. Source: https://developers.tiktok.com/docs/en/tiktok-api-v2-video-query. This reference alias is restricted to the connected user’s own account and official Query Videos source; it checks the URL username and TikTok verifies video ownership. Transcripts, arbitrary creators, region routing, and downloads are unavailable. |
Transcript | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Live | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Live Info | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Comments | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Comment Replies | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Following | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Followers | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Search Users | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Search Suggestions | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Search by Hashtag | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Search by Keyword | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Top Search | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Get Song Details | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
TikToks using Song | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Trending Feed | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Get popular songs | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
Get popular videos | planned · not implemented · source review required | Source review required before implementation: automated collection and commercial reuse need authorization for this product and method. TikTok live extraction remains unverified from this deployment region. See the source gate in docs/LAUNCH.md. Source: https://t.tiktok.com/legal/page/us/terms-of-service/en. |
TikTok Shop
| Field | Type | Description |
|---|---|---|
Shop Search | implemented · local checks only · production blocked by default | GET /v1/tiktok/shop/search (catalog path). GET /api/v1/tiktok-shop/products. Owner-authorized partial mapping to TikTok Shop Partner Center Affiliate Creator `Get Shop Products` (`GET /affiliate_creator/202509/shop_products`). The request is allowed only for the exact connected TikTok Shop marketing or official account whose current creator profile matches the submitted handle and selection region; affiliate creators use the separate showcase operation. SignalShelf maps `query` to `title_keyword`, signs the official request, supports its documented 1–20 `page_size`, sort fields, and opaque `page_token` cursor. The reference numeric `page` parameter is accepted only as 1 because it cannot safely map to TikTok Shop’s opaque continuation token. Requires the exact creator scope selected for Get Shop Products in Partner Center to be set as `TIKTOK_SHOP_PRODUCTS_SCOPE`; the public docs reviewed do not state the string scope key, so do not guess it. Affiliate API activation, creator authorization allowlisting, app/compliance review, paid-use/retention clearance, and live validation remain outstanding; production is blocked by default. Local HTTP fixture evidence only; no app credentials or live calls. This cannot search arbitrary shops or accounts. Sources: https://partner.tiktokshop.com/docv2/page/affiliate-integration, https://partner.tiktokshop.com/docv2/page/creator-authorization-guide, and https://partner.tiktokshop.com/docv2/page/ng0l9170. |
Shop Products | planned · not implemented · source review required | Source review required before implementation: distinguish Affiliate Creator shop-bound product search from the catalog’s public store-URL lookup. Official Seller Product Search requires seller OAuth and an authorized shop; the Bestsellers API is seller/market scoped and limited to 100 ranked products with GMV ranges. Neither documents the reference public shop aggregates or top/new_releases ordering. Obtain exact Partner Center scopes, seller authorization, paid display/redistribution and retention clearance before a seller-only partial. TikTok’s official Research API documents EU product reviews at POST /v2/research/tts/review/ with research.data.basic and page_size up to 10, but the API is limited to approved noncommercial public-interest research and cannot power this paid service. Partner Center lists Customer Reviews as an app category, but an app category is not an API permission: the reviewed public API reference still does not establish a seller-authorized customer-review read endpoint/scope. In Partner Center, verify the exact scopes available for the accurately selected app type/category and request the documented read contract from the Partner Manager/support if absent; public or connector app review requirements apply as shown in the app workflow. Get Review Decisions is an aftersales return-decision API, not a review feed. The separately documented US SPS NRR problem-details API is from the previous SPS version; TikTok says the new US SPS replaced it on October 15, 2026 and legacy SPS API scores/rules are reference only while new SPS APIs are pending. Do not treat legacy NRR data as a current product substitute. Sources: https://docs.scrapecreators.com/v1/tiktok/shop/products/, https://partner.tiktokshop.com/docv2/page/6503081a56e2bb0289dd6d7d, https://partner.tiktokshop.com/docv2/page/3dk9557y, https://developers.tiktok.com/docs/en/research-api-specs-query-tiktok-shop-reviews, https://developers.tiktok.com/products/research-api/, https://partner.tiktokshop.com/docv2/page/hulvi36o, https://partner.tiktokshop.com/docv2/page/app-review-process, https://partner.tiktokshop.com/docv2/page/1nj6l9ok, https://partner.tiktokshop.com/docv2/page/5daswqdc, and https://partner.tiktokshop.com/docv2/page/ph0ccose. |
Product Details | implemented · local checks only · production blocked by default | GET /v1/tiktok/product (catalog path). GET /api/v1/tiktok-shop/product-details. Owner-authorized partial mapping to TikTok Shop Affiliate Creator Get Open Collaboration Product List By Product IDs (`POST /affiliate_creator/202509/open_collaborations/products`). Accepts only canonical `shop.tiktok.com/view/product/{id}` or `www.tiktok.com/view/product/{id}` URLs with numeric product IDs; short links are rejected without redirect resolution. It queries the exact ID only with the caller’s connected TikTok Shop creator access token and `creator.affiliate_collaboration.read`, then returns the product only if TikTok Shop includes that exact ID in the creator’s open-collaboration marketplace and the sale region matches. It does not provide arbitrary product details or seller inventory. Local fixture verification only; affiliate API activation/allowlisting, app review, written paid-use and retention clearance, and live validation remain outstanding; production stays gated. Sources: https://partner.tiktokshop.com/docv2/page/get-open-collaboration-product-list-by-product-ids-202509, https://partner.tiktokshop.com/docv2/page/creator-authorization-guide, and https://partner.tiktokshop.com/docv2/page/affiliate-integration. |
Product Reviews | planned · not implemented · source review required | Source review required before implementation: distinguish Affiliate Creator shop-bound product search from the catalog’s public store-URL lookup. Official Seller Product Search requires seller OAuth and an authorized shop; the Bestsellers API is seller/market scoped and limited to 100 ranked products with GMV ranges. Neither documents the reference public shop aggregates or top/new_releases ordering. Obtain exact Partner Center scopes, seller authorization, paid display/redistribution and retention clearance before a seller-only partial. TikTok’s official Research API documents EU product reviews at POST /v2/research/tts/review/ with research.data.basic and page_size up to 10, but the API is limited to approved noncommercial public-interest research and cannot power this paid service. Partner Center lists Customer Reviews as an app category, but an app category is not an API permission: the reviewed public API reference still does not establish a seller-authorized customer-review read endpoint/scope. In Partner Center, verify the exact scopes available for the accurately selected app type/category and request the documented read contract from the Partner Manager/support if absent; public or connector app review requirements apply as shown in the app workflow. Get Review Decisions is an aftersales return-decision API, not a review feed. The separately documented US SPS NRR problem-details API is from the previous SPS version; TikTok says the new US SPS replaced it on October 15, 2026 and legacy SPS API scores/rules are reference only while new SPS APIs are pending. Do not treat legacy NRR data as a current product substitute. Sources: https://docs.scrapecreators.com/v1/tiktok/shop/products/, https://partner.tiktokshop.com/docv2/page/6503081a56e2bb0289dd6d7d, https://partner.tiktokshop.com/docv2/page/3dk9557y, https://developers.tiktok.com/docs/en/research-api-specs-query-tiktok-shop-reviews, https://developers.tiktok.com/products/research-api/, https://partner.tiktokshop.com/docv2/page/hulvi36o, https://partner.tiktokshop.com/docv2/page/app-review-process, https://partner.tiktokshop.com/docv2/page/1nj6l9ok, https://partner.tiktokshop.com/docv2/page/5daswqdc, and https://partner.tiktokshop.com/docv2/page/ph0ccose. |
User Showcase | implemented · local checks only · production blocked by default | GET /v1/tiktok/user/showcase (catalog path). GET /api/v1/tiktok-shop/showcase. Owner-authorized partial mapping to the official TikTok Shop Affiliate Creator Get Showcase Products API. The caller must connect the exact creator account and grant creator.showcase.read (or the documented alternative creator.video.write); requests verify the current creator profile username and selection region against the supplied handle/region. Uses official OAuth creator tokens, encrypted durable token storage, signed Partner Center requests, page_token pagination capped at 20, and a per-SignalShelf-user cache. Affiliate API activation, creator authorization allowlisting, app/compliance review, paid-use/retention clearance, and live validation remain outstanding; production is blocked by default. The catalog’s arbitrary public handle contract is not supported. Local HTTP fixture evidence only; no TikTok Shop app credentials or live provider calls. Sources: https://partner.tiktokshop.com/docv2/page/affiliate-integration, https://partner.tiktokshop.com/docv2/page/creator-authorization-guide, https://partner.tiktokshop.com/docv2/page/get-showcase-products-202405, and https://partner.tiktokshop.com/docv2/page/common-parameters. |
| Field | Type | Description |
|---|---|---|
Profile | implemented · local checks only · production blocked by default | GET /v1/instagram/profile (catalog path). GET /v1/instagram/profile. Partial official-source mapping through Meta Graph API Facebook Login Business Discovery. The caller must connect a managed Page linked to an Instagram professional account. Exact-handle lookup is limited to discoverable public Business/Creator targets; consumer, private, unavailable, and non-professional accounts are not exposed. Returns only allowlisted fields provided by Meta: username, name, biography, profile image, followers, media count, and website. Following count, recent media, related profiles, category, and verification status are unavailable and are not synthesized. One-hour cache; `trim` is accepted. Reconnecting or disconnecting purges this user’s Instagram-specific cached data. `npm run test:instagram-business-discovery-simulation` passed through the local Postman Graph mock for public profile field mapping, cache behavior, unavailable/mismatched profiles, account isolation, and disconnect cache cleanup; `npm run test:instagram-facebook` passed its OAuth reconnect cache-cleanup regression. Both used local fixtures only; no live Meta request was made. Field availability, app approval, live validation, retention, and written paid-redistribution clearance remain outstanding. Production remains source-gated. Source: https://www.postman.com/meta/instagram/documentation/6yqw8pt/instagram-api. |
Basic Profile | implemented · local checks only · production blocked by default | GET /v1/instagram/basic-profile. Uses official Instagram Login for the professional account explicitly connected to this SignalShelf user. It does not resolve arbitrary usernames or read another account. Field mapping is intentionally partial and limited to Meta-returned user_id, username, account_type, media_count, followers_count, and follows_count on this connected professional account; count fields may be omitted if the API does not return them. OAuth configuration and Meta app approval are required; production remains disabled by default. |
Posts | implemented · local checks only · production blocked by default | GET /v2/instagram/user/posts. Partial mapping supports two official access paths: the Instagram Login token reads posts only from the professional account connected to this SignalShelf user; a separate Page-linked professional Instagram connection can use Meta Business Discovery for the exact requested username when it identifies a public Business or Creator account. Business Discovery returns only allowlisted id, caption, media type, permalink, thumbnail, and timestamp fields; it does not expose a media URL or play counts here. Pagination uses the source cursor as next_max_id and is capped at 25 per page. Consumer/private or undiscoverable profiles, arbitrary user_id lookup, trim, play counts, and tagged media are unsupported. `npm run test:instagram-business-discovery-simulation` passed through the local Postman Graph mock for public profile and post mapping, two cursor pages, cache behavior, omitted fields, unavailable/mismatched profiles, and connected-account isolation; no live Meta request was made. Production remains blocked pending Meta app review and written clearance for SignalShelf’s paid use, caching, and retention. Sources: https://www.postman.com/meta/instagram/documentation/6yqw8pt/instagram-api and https://developers.facebook.com/documentation/instagram-platform/instagram-graph-api/reference/ig-user/business_discovery. |
User Tagged Posts | implemented · local checks only · production blocked by default | GET /v1/instagram/user/tagged-posts (catalog path). GET /v1/instagram/user/tagged-posts. Uses Meta Graph API Facebook Login and the official Instagram User tags edge. Reads only a professional Instagram account that this same SignalShelf user explicitly connected through a Page they manage; user_id must match that connected account. Returns only source-backed media identifiers, caption, type, URLs, timestamp, and username when provided. Cursor paging maps to Meta’s `after` cursor, with up to 25 items per page. This is not arbitrary-handle lookup or private-account access. Local simulation only; app approval, live validation, and written clearance for paid redistribution remain outstanding. Production remains source-gated. Sources: https://www.postman.com/meta/instagram/documentation/6yqw8pt/instagram-api and https://www.facebook.com/legal/automated_data_collection_terms. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Reels | implemented · local checks only · production blocked by default | GET /v1/instagram/user/reels (catalog path). GET /v1/instagram/user/reels. Partial official-source mapping through Meta Graph API Facebook Login. The app user connects a managed Page linked to an Instagram professional account; Meta Business Discovery can then return public media from other Business or Creator accounts by exact username. The target must be a discoverable professional account; personal/consumer, private, unavailable, and non-professional accounts are not exposed. Results are filtered to source-tagged REELS and include allowlisted metadata. The connected account can also read its own media edge. `max_id` maps to the nested Graph `media.after` cursor; page size is capped at 25. `require_play_counts=true` is rejected because the source field set does not provide that catalog metric. `npm run test:instagram-business-discovery-simulation` passed through the local Postman Graph mock for source-tagged Reel filtering, allowlisted profile/media fields, two cursor pages, cache behavior, unsupported play-count rejection, and an undiscoverable target; no live Meta request was made. Exact live field availability, app approval, retention, and written clearance for paid redistribution remain outstanding. Production remains source-gated. Sources: https://www.postman.com/meta/instagram/documentation/6yqw8pt/instagram-api and https://developers.facebook.com/documentation/instagram-platform/instagram-graph-api/reference/ig-user/media. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Post/Reel Info | implemented · local checks only · production blocked by default | GET /v1/instagram/post. Reference GET alias is locally tested over SignalShelf public post/reel metadata. It does not provide persistent media downloads or source-region routing; response field parity remains partial and live alias behavior has not been verified. |
Transcript | planned · not implemented · source review required | Source review required before implementation: Meta requires permission for automated collection from its services. See the source gate in docs/LAUNCH.md. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
Search Instagram | planned · not implemented · source review required | Source review required before implementation: Meta requires permission for automated collection from its services. See the source gate in docs/LAUNCH.md. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
Popular Search | planned · not implemented · source review required | Source review required before implementation: Meta requires permission for automated collection from its services. See the source gate in docs/LAUNCH.md. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
Search Hashtag Posts | implemented · local checks only · production blocked by default | GET /v1/instagram/search/hashtag (catalog path). GET /v1/instagram/search/hashtag. Partial owner-authorized public-content mapping through Meta Graph API Facebook Login hashtag search. The caller must connect a Page-linked professional Instagram account; Meta must approve Instagram Public Content Access. SignalShelf checks Meta’s recently-searched-hashtag edge before requesting the public recent_media page, which contains media from the previous 24 hours, so a new unique hashtag is rejected when the source account has reached the documented maximum of 30 unique hashtags in a rolling seven days. Cursor pagination is mapped. date_posted windows and a reliable Reels-only filter are unsupported and explicitly rejected; source attribution/usernames are not returned. `npm run test:instagram-business-discovery-simulation` passed through the local Postman Graph mock for search resolution, two media pages, cache behavior, creator-field omission, unsupported filters, and the 30-unique-hashtag quota; no live Meta request was made. App review, live field validation, retention review, and written paid-use clearance remain outstanding; production stays blocked. Sources: https://www.postman.com/meta/instagram/documentation/6yqw8pt/instagram-api and https://developers.facebook.com/documentation/instagram-platform/instagram-graph-api/reference/ig-hashtag-search. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Search Instagram Profiles | implemented · local checks only · production blocked by default | GET /v1/instagram/search/profiles (catalog path). GET /v1/instagram/search/profiles. Partial opt-in discovery through Meta Instagram Creator Marketplace `/{ig-user-id}/creator_marketplace_creators?query=...`. This is a Marketplace recommendation/search set for the eligible connected brand, not unrestricted public-profile search, arbitrary handle lookup, or private-account access. Requests only id, username, biography, category, country, profile picture URL, verified status, and badges; sensitive contact, gender, audience, and messaging fields are not requested or returned. Facebook Login for Business must include `instagram_creator_marketplace_discovery` plus the documented base scopes; Meta Advanced Access, eligible brand onboarding, and approved paid use are required. Source `after` cursors are supported as an optional continuation parameter. OAuth requests the Marketplace scope only when `INSTAGRAM_CREATOR_MARKETPLACE_SCOPE_ENABLED=true`; live production also requires all source authorization flags. `npm run test:instagram-business-discovery-simulation` passed against a local Graph fixture for the route, allowlisting, cache, permission-denial refund, production gate, disconnected-user isolation, and cache deletion. No live Meta request was made; exact live fields, app review, customer redistribution, and retention remain unverified, so production stays blocked. Sources: https://github.com/facebookincubator/catalogue-of-api-solutions/blob/main/solutions/creators/creator-discovery.md and https://github.com/meta/facebook-php-business-sdk/blob/main/src/FacebookAds/Object/IGUser.php. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Search Reels | planned · not implemented · source review required | Source review required before implementation: Meta requires permission for automated collection from its services. See the source gate in docs/LAUNCH.md. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
Get Reels By Audio Id | planned · not implemented · source review required | Source review required before implementation: Meta requires permission for automated collection from its services. See the source gate in docs/LAUNCH.md. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
Trending Reels | planned · not implemented · source review required | Source review required before implementation: Meta requires permission for automated collection from its services. See the source gate in docs/LAUNCH.md. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
Comments | implemented · local checks only · production blocked by default | GET /v2/instagram/post/comments (catalog path). GET /v2/instagram/post/comments. Partial owner-authorized mapping via Meta Graph API Facebook Login. The supplied canonical post/Reel URL must resolve by permalink in the first 75 items of a Page-linked Instagram professional account connected by this same SignalShelf user; Meta comments are then fetched for that owned media only. Returns up to 50 comments per page with a Meta cursor and allowlisted text, timestamp, public username, and like count when supplied. It does not retrieve comments for arbitrary creators, nested replies, or private media. Requires `instagram_manage_comments`; local simulation only, no Meta app credentials or live request. App review, source/field validation, retention and written paid-distribution clearance remain open; production stays gated. Sources: https://www.postman.com/meta/instagram/documentation/6yqw8pt/instagram-api and https://developers.facebook.com/docs/instagram-platform/instagram-api-with-instagram-login/comment-moderation. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Comment Replies | implemented · local checks only · production blocked by default | GET /v1/instagram/post/comment/replies (catalog path). GET /v1/instagram/post/comment/replies. Partial owner-authorized mapping via Meta Graph API Facebook Login. SignalShelf resolves the supplied canonical post/Reel URL only against the first 75 media items on a Page-linked professional account connected by this same SignalShelf user, then confirms the supplied comment_id appears in the first 250 comments on that owned media before requesting its replies. Returns up to 50 source replies per page with a Meta cursor and allowlisted text, timestamp, public username, and like count when provided. No arbitrary posts, private media, unrelated comment IDs, or stable commenter IDs are exposed. Requires `instagram_manage_comments`; local simulation only, no Meta app credentials or live request. App review, field validation, retention, and written paid-distribution clearance remain open; production stays gated. Sources: https://www.postman.com/meta/instagram/documentation/6yqw8pt/instagram-api and https://developers.facebook.com/docs/instagram-platform/instagram-api-with-instagram-login/comment-moderation. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Story Highlights | planned · not implemented · source review required | Not implemented: Meta’s supported Instagram API contract covers eligible professional-account media and ephemeral Stories access, but no reviewed endpoint establishes listing saved Story Highlight collections for arbitrary profiles. The official Meta collection does not document a Highlights edge. Do not substitute current Stories for saved Highlights. Revisit only if Meta provides written approval and a current endpoint contract, or a licensed source that permits this exact paid lookup. Sources: https://www.postman.com/meta/instagram/documentation/6yqw8pt/instagram-api and https://developers.facebook.com/legal/terms/. |
Highlights Details | planned · not implemented · source review required | Not implemented: no reviewed Meta Instagram API contract establishes retrieval of stories inside saved Highlights, especially for arbitrary profiles. Current Stories access is not evidence of access to archived Highlight contents. Do not fetch media using browser automation or undocumented endpoints. Revisit only with a written approved source contract covering highlight ownership/access, media fields, retention, and paid redistribution. Sources: https://www.postman.com/meta/instagram/documentation/6yqw8pt/instagram-api and https://developers.facebook.com/legal/terms/. |
Profile Post Count | implemented · local checks only · production blocked by default | GET /v1/instagram/profile/post-count (catalog path). GET /api/v1/instagram/profile/post-count. Partial official-source mapping through Meta Graph API Facebook Login Business Discovery. Both `/v1/instagram/profile/post-count` and `/api/v1/instagram/profile/post-count` require the caller to connect a managed Page linked to an Instagram professional account. Exact-handle lookup is limited to discoverable public Business/Creator targets; consumer, private, unavailable, and non-professional accounts are unavailable. Uses only Meta’s `media_count` field and returns it as the public media count; the compatibility `allow_estimated` flag is accepted but has no effect because this source returns a numeric count, not an abbreviated page estimate. One-hour cache is shared by native and reference paths. `npm run test:instagram-business-discovery-simulation` passed for the exact count field, owner connection requirement, and native/reference cache reuse; no live Meta request was made. App approval, live validation, retention, and written paid-redistribution clearance remain outstanding. Production remains source-gated. Source: https://www.postman.com/meta/instagram/documentation/6yqw8pt/instagram-api. |
Embed HTML | planned · not implemented · source review required | The reference contract accepts a profile handle and returns a full HTML document. Meta’s official `instagram_oembed` API is an embedding source with use restricted to front-end rendering; it does not establish a supported full profile-page HTML response or permission to reuse page HTML as creator data. A live tokenless request to Meta Graph API v25.0 for the public `instagram` profile returned `Invalid URL` / “does not refer to an embeddable media.” Keep this operation planned until Meta documents a profile embed response and its use for this specific front-end feature is cleared. Do not substitute a logged-out profile-page fetch or extract page data from the embed. Sources: https://developers.facebook.com/documentation/instagram-platform/oembed and https://github.com/meta/meta-embeds-for-wordpress. |
Reels using Song (Deprecated) | planned · not implemented · source review required · reference provider deprecated | Scrape Creators marks this operation deprecated. Do not treat it as a current supported operation. Source review required before implementation: Meta requires permission for automated collection from its services. See the source gate in docs/LAUNCH.md. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
YouTube
| Field | Type | Description |
|---|---|---|
Channel Details | implemented · live checked · production blocked by default | GET /v1/youtube/channel (catalog path). GET /v1/youtube/channel. Reference GET alias accepts a public handle, channel ID, or supported canonical URL and reuses SignalShelf public channel profile parsing. Live check for NASA returned a channel ID, canonical URL, name, numeric/formatted counts, joined-date text, keyword array, avatar/banner sources, and public social links including the Scrape Creators `x` field alias; a repeated request reused cache for zero credits. Only explicitly linked store URLs are mapped; vendor-specific dynamic link keys, contact email, and unsupported policy fields are omitted. Public-page fields and channel scope can vary; response parity remains partial and production is source-gated. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. |
Channel Videos | implemented · live checked · production blocked by default | GET /v1/youtube/channel-videos (catalog path). GET /api/v1/youtube/channel-videos. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. Latest strict live app recheck on 2026-11-02 returned 30 public NASA Videos-tab cards on each of two pages and charged two disposable credits. A prior first attempt returned a transient 502 with no debit; immediate retry succeeded. This public-page snapshot does not establish complete archive coverage or stable availability. |
Channel Search | implemented · live checked · production blocked by default | GET /v1/youtube/channel/search (catalog path). GET /api/v1/youtube/channel/search. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. Latest strict live app recheck on 2026-11-02 returned 14 videos, 10 Shorts, and five playlists for a NASA channel search. An earlier batch briefly returned UPSTREAM_UNAVAILABLE before a successful sequential retry; the latest run had no upstream errors. Public search availability is point-in-time and can vary. |
Channel Playlists | implemented · live checked · production blocked by default | GET /v1/youtube/channel/playlists (catalog path). GET /api/v1/youtube/channel/playlists. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. |
Channel Lives | implemented · live checked · production blocked by default | GET /v1/youtube/channel/lives (catalog path). GET /api/v1/youtube/channel/lives. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. |
Channel Community Posts | implemented · live checked · production blocked by default | GET /v1/youtube/channel/community-posts (catalog path). GET /api/v1/youtube/channel/community-posts. The public NASA channel Posts tab was live-checked through the authenticated SignalShelf app, including two pages, image/video attachments, cache reuse, and the reference route alias. Post fields depend on what YouTube publicly exposes. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. |
Channel Shorts | implemented · live checked · production blocked by default | GET /v1/youtube/channel/shorts (catalog path). GET /api/v1/youtube/channel/shorts. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. |
Video/Short Details | implemented · live checked · production blocked by default | GET /v1/youtube/video (catalog path). GET /api/v1/youtube/video. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. Focused live app recheck on 2026-11-02 returned public video details for dQw4w9WgXcQ, then cache_max_age=1d reused the response as a zero-credit cache hit. One fresh disposable credit was charged. This verifies cache-age acceptance and billing for this sample; response parity and source clearance remain separate. |
Transcript | implemented · local checks only · production blocked by default | GET /v1/youtube/video/transcript (catalog path). POST /api/v1/youtube/video/transcript. Owner-authorized partial mapping through YouTube Data API captions.list and captions.download. The video must belong to the YouTube channel connected to the same SignalShelf user and that account must have permission to edit the video; arbitrary public-video transcript lookup is unavailable. OAuth uses the broad youtube.force-ssl scope, tokens are encrypted, results are private to the authorizing user, authorization is rechecked before cache reads, and transcript cache is capped at seven days. Daily provider attempts are capped. Local Postman simulation only; Google OAuth, live caption behavior, application verification, and paid-use clearance are outstanding. Production stays source-gated. Sources: https://developers.google.com/youtube/data/reference/rest/v3/captions/list, https://developers.google.com/youtube/data/reference/rest/v3/captions/download, and https://developers.google.com/youtube/terms/developer-policies. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. |
Video Sponsors | implemented · live checked · production blocked by default | GET /v1/youtube/video/sponsors (catalog path). GET /api/v1/youtube/video/sponsors. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The reference path returns inferred sponsor candidates from public badge/description/link evidence with SignalShelf credit and cache metadata. It does not use transcript evidence; no match does not prove the video is unsponsored. |
Search | implemented · live checked · production blocked by default | GET /v1/youtube/search (catalog path). GET /api/v1/youtube/search. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. Latest live app rechecks on 2026-11-02 returned 12 default NASA Artemis results; type filters returned 20 videos, 25 Shorts, 20 channels, and 20 playlists; combined uploadDate=today, sortBy=popular, duration=under_3_min, type=videos returned four videos; region=IN returned 16 results on page one and nine on its continuation. The vendor defines region as proxy location; SignalShelf maps it only to YouTube’s public gl setting and does not claim proxy-location parity. No proxy or account session was used. Results are point-in-time, and production remains source-gated. |
Search Typeahead | implemented · live checked · production blocked by default | GET /v1/youtube/search/typeahead (catalog path). GET /api/v1/youtube/search/typeahead. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. |
Search by Hashtag | implemented · live checked · production blocked by default | GET /v1/youtube/search/hashtag (catalog path). GET /api/v1/youtube/search/hashtag. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. Latest strict live app recheck on 2026-11-02 returned three public results for the shorts hashtag. An earlier batch briefly returned UPSTREAM_UNAVAILABLE before a successful sequential retry; the latest run had no upstream errors. The new type=shorts filter passed local fixtures, but its follow-up live run received UPSTREAM_UNAVAILABLE after an earlier request succeeded; this parameter variant is not yet live-verified. Results and availability can vary by time and region. |
Comments | implemented · live checked · production blocked by default | GET /v1/youtube/video/comments (catalog path). GET /api/v1/youtube/video/comments. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. |
Comment Replies | implemented · live checked · production blocked by default | GET /v1/youtube/video/comment/replies (catalog path). GET /api/v1/youtube/video/comment/replies. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. |
Trending Shorts | planned · not implemented · source review required | No official public Shorts-trending API is documented. YouTube’s revision history says `videos.list(chart=mostPopular)` stopped reflecting the Trending Now page on July 21, 2025 and now serves Trending Music, Movies, and Gaming; the API reference does not define a Shorts category. `search.list(videoDuration=short)` means videos under four minutes, not Shorts classification or trend ranking, and `fileDetails` dimensions are owner-only. YouTube Studio Trends is authenticated and audience-specific. Do not relabel any of those sources as global Shorts trends. Keep this route unavailable pending an approved matching source and public data contract. Sources: https://developers.google.com/youtube/data/reference/rest/v3/videos/list, https://developers.google.com/youtube/data/guides/implementation/videos, https://developers.google.com/youtube/data/reference/rest/v3/search/list, https://developers.google.com/youtube/data/reference/rest/v3/videos, https://developers.google.com/youtube/data/revision_history, and https://support.google.com/youtube/answer/11962757. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. |
Playlist | implemented · live checked · production blocked by default | GET /v1/youtube/playlist (catalog path). GET /api/v1/youtube/playlist. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; this reference path exposes resource-specific fields, success, and SignalShelf account credit values alongside data/meta. Available fields and options depend on the public source reader; only source-backed public data is returned. |
Community Post Details | implemented · live checked · production blocked by default | GET /v1/youtube/community-post (catalog path). GET /api/v1/youtube/community-post. Public NASA and multi-image community posts passed live checks through the authenticated SignalShelf app. The reader returns all exposed images and uses an absolute timestamp only if YouTube provides one; visible like counts can be rounded. Private or unavailable posts are not exposed. Production live access is disabled by default until the YouTube source method and cross-channel commercial use are authorized. The native /api/v1 route keeps the standard SignalShelf envelope; the reference path exposes public post fields and SignalShelf credit values alongside data/meta. All visible images are returned; absolute time is returned only when provided by the source, and displayed like counts can be rounded. |
Rumble
| Field | Type | Description |
|---|---|---|
Search | planned · not implemented · source review required | Not implemented. Rumble Website Terms (last modified 2026-09-01) prohibit automated software access without prior written permission and systematic retrieval to create/compile a collection or database without prior written permission; they also restrict commercial use, distribution, copying, and exploitation of Content absent express authorization. Rumble documents a separate Live Stream API that is a creator-controlled secret URL for that creator’s own live-stream telemetry, not a public channel discovery, archive, search, or comments API. It cannot establish access for arbitrary creators or provide a substitute for these routes. Keep all catalog routes unavailable until written Rumble permission expressly covers automated access, exact data fields, dataset/aggregation, paid customer delivery/redistribution, content links/text, and retention/deletion. Sources: https://rumble.com/s/terms and https://rumble.support/help/how-to-use-rumble-s-live-stream-api. |
Channel Videos | planned · not implemented · source review required | Not implemented. Rumble Website Terms (last modified 2026-09-01) prohibit automated software access without prior written permission and systematic retrieval to create/compile a collection or database without prior written permission; they also restrict commercial use, distribution, copying, and exploitation of Content absent express authorization. Rumble documents a separate Live Stream API that is a creator-controlled secret URL for that creator’s own live-stream telemetry, not a public channel discovery, archive, search, or comments API. It cannot establish access for arbitrary creators or provide a substitute for these routes. Keep all catalog routes unavailable until written Rumble permission expressly covers automated access, exact data fields, dataset/aggregation, paid customer delivery/redistribution, content links/text, and retention/deletion. Sources: https://rumble.com/s/terms and https://rumble.support/help/how-to-use-rumble-s-live-stream-api. |
Video | planned · not implemented · source review required | Not implemented. Rumble Website Terms (last modified 2026-09-01) prohibit automated software access without prior written permission and systematic retrieval to create/compile a collection or database without prior written permission; they also restrict commercial use, distribution, copying, and exploitation of Content absent express authorization. Rumble documents a separate Live Stream API that is a creator-controlled secret URL for that creator’s own live-stream telemetry, not a public channel discovery, archive, search, or comments API. It cannot establish access for arbitrary creators or provide a substitute for these routes. Keep all catalog routes unavailable until written Rumble permission expressly covers automated access, exact data fields, dataset/aggregation, paid customer delivery/redistribution, content links/text, and retention/deletion. Sources: https://rumble.com/s/terms and https://rumble.support/help/how-to-use-rumble-s-live-stream-api. |
Transcript | planned · not implemented · source review required | Not implemented. Rumble Website Terms (last modified 2026-09-01) prohibit automated software access without prior written permission and systematic retrieval to create/compile a collection or database without prior written permission; they also restrict commercial use, distribution, copying, and exploitation of Content absent express authorization. Rumble documents a separate Live Stream API that is a creator-controlled secret URL for that creator’s own live-stream telemetry, not a public channel discovery, archive, search, or comments API. It cannot establish access for arbitrary creators or provide a substitute for these routes. Keep all catalog routes unavailable until written Rumble permission expressly covers automated access, exact data fields, dataset/aggregation, paid customer delivery/redistribution, content links/text, and retention/deletion. Sources: https://rumble.com/s/terms and https://rumble.support/help/how-to-use-rumble-s-live-stream-api. |
Comments | planned · not implemented · source review required | Not implemented. Rumble Website Terms (last modified 2026-09-01) prohibit automated software access without prior written permission and systematic retrieval to create/compile a collection or database without prior written permission; they also restrict commercial use, distribution, copying, and exploitation of Content absent express authorization. Rumble documents a separate Live Stream API that is a creator-controlled secret URL for that creator’s own live-stream telemetry, not a public channel discovery, archive, search, or comments API. It cannot establish access for arbitrary creators or provide a substitute for these routes. Keep all catalog routes unavailable until written Rumble permission expressly covers automated access, exact data fields, dataset/aggregation, paid customer delivery/redistribution, content links/text, and retention/deletion. Sources: https://rumble.com/s/terms and https://rumble.support/help/how-to-use-rumble-s-live-stream-api. |
| Field | Type | Description |
|---|---|---|
Person's Profile | planned · not implemented · source review required | Not implemented: LinkedIn’s Profile API is restricted to approved developers and authenticated members; the documentation permits storing returned profile data only for the authenticated member with permission and prohibits storing other members’ profile data. It cannot support arbitrary public member-profile lookup. LinkedIn API Terms also prohibit stand-alone API distribution and incremental fees for access to LinkedIn Content, and the self-serve program excludes applications that rely on API access as a fundamental business aspect. Sources: https://learn.microsoft.com/en-us/linkedin/shared/integrations/people/profile-api and https://www.linkedin.com/legal/l/api-terms-of-use. |
Company Page | implemented · local checks only · production blocked by default | GET /v1/linkedin/company (catalog path). GET /v1/linkedin/company. Reference GET alias accepts public LinkedIn company URLs only; personal profiles are not supported. Live alias behavior is unverified and production is source-gated. |
Company Posts | planned · not implemented · source review required | Not implemented: LinkedIn Posts API can retrieve organization posts only with the vetted Community Management API and `r_organization_social`; access is restricted to organizations where the authenticated member has an eligible Page role. This is not arbitrary public company-post lookup. LinkedIn API Terms prohibit stand-alone API distribution and incremental fees for LinkedIn Content; SignalShelf needs written program approval for this paid API model before implementation. Sources: https://learn.microsoft.com/en-us/linkedin/marketing/community-management/shares/posts-api and https://learn.microsoft.com/en-us/linkedin/marketing/community-management/community-management-overview. |
Search Posts | planned · not implemented · source review required | Not implemented: the reviewed LinkedIn Posts API documents author-based retrieval and does not establish a general public keyword search for arbitrary posts matching this catalog route. Member post read permission is restricted, while organization posts require approved Community Management access and an authorized Page role. LinkedIn terms prohibit stand-alone API distribution and incremental content fees. Obtain explicit written program/product approval and a matching search contract. Sources: https://learn.microsoft.com/en-us/linkedin/marketing/community-management/shares/posts-api and https://www.linkedin.com/legal/l/api-terms-of-use. |
Post | planned · not implemented · source review required | Not implemented: LinkedIn Posts API can fetch posts through documented IDs/URNs within its permission model, but no reviewed contract establishes arbitrary public URL-to-post lookup for this catalog operation. Member and organization post access is restricted by approved scopes and account roles. LinkedIn terms prohibit stand-alone API distribution and incremental fees for content; written approval is required for SignalShelf’s paid access model. Sources: https://learn.microsoft.com/en-us/linkedin/marketing/community-management/shares/posts-api and https://www.linkedin.com/legal/l/api-terms-of-use. |
Post Transcript | planned · not implemented · source review required | Not implemented: LinkedIn’s reviewed APIs do not document a post video transcript operation. Obtaining video media and creating transcript text would require a separately authorized media source and rights for transcription, retention, and redistribution. LinkedIn API Terms also prohibit stand-alone API distribution and incremental fees for LinkedIn Content. Obtain written LinkedIn approval and a licensed transcription/media contract before implementation. Sources: https://learn.microsoft.com/en-us/linkedin/marketing/community-management/shares/posts-api and https://www.linkedin.com/legal/l/api-terms-of-use. |
| Field | Type | Description |
|---|---|---|
Profile | implemented · local checks only · production blocked by default | GET /v1/facebook/profile (catalog path). GET /api/v1/facebook/profile. Partial owner-authorized mapping through Meta Graph API Facebook Login. Only a numeric Facebook Page ID that appears in this same SignalShelf user’s connected Page-linked Instagram account records is readable; the request is rejected before egress for arbitrary or personal profiles. The API returns an allowlist of public Page metadata and omits contact, gated, and unknown fields. Requires an eligible managed Page linked to a connected Instagram professional account, `pages_read_engagement`, Meta app review, and the dedicated production gate. Local Meta Graph simulation only; no Meta credentials or live request. Written paid-use clearance and live field validation remain outstanding. Sources: https://www.postman.com/meta/instagram/documentation/6yqw8pt/instagram-api and https://developers.facebook.com/docs/graph-api/reference/page/. |
Profile Reels | planned · not implemented · source review required | Not implemented: the reviewed Meta Graph API Page Videos contract does not establish a read operation for listing Page videos/Reels; the documented Reels API is for publishing. This is not evidence that every possible approved partner capability is unavailable, but no current public read contract matching arbitrary Page/profile Reels, pagination, and paid SignalShelf delivery has been identified. Do not alias ordinary Page videos to Reels or use browser/session/proxy extraction. Unblock only with written Meta approval and a current versioned read contract (or a licensed source) covering the exact Page relationship, fields, pagination, regions, and paid redistribution. If approval covers only Pages the caller manages, redesign around a connected Page and mark owner-authorized partial coverage. Sources: https://developers.facebook.com/docs/graph-api/reference/page/videos/ and https://www.postman.com/meta/facebook/documentation/r56bjfd/facebook-api. |
Search Videos | planned · not implemented · source review required | Source review required before implementation: Meta requires permission for automated collection from its services. See the source gate in docs/LAUNCH.md. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
Profile Photos | implemented · local checks only · production blocked by default | GET /v1/facebook/profile/photos (catalog path). GET /api/v1/facebook/profile/photos. Partial owner-authorized mapping through the official Meta Graph API Page Photos edge. Requires the exact numeric Page ID connected to this SignalShelf user, a valid Page access token with `pages_read_engagement` and `pages_show_list`, and a person with the Page `MODERATE` task unless the app has approved Page Public Content Access. Reads only uploaded Page photos, requests allowlisted fields, and maps the Graph `after` cursor to both `cursor` and `next_page_id`; the two input cursor aliases must match if both are supplied. Vanity URLs, arbitrary Pages, profile-picture history, visitor photos, media downloads, and unsupported fields are unavailable. Local Meta Graph simulation only; no Meta credentials or live request. Written app/paid-use/retention clearance and live field validation remain outstanding. Sources: https://developers.facebook.com/docs/graph-api/reference/page/photos/ and https://developers.facebook.com/docs/graph-api/reference/page/. |
Profile Posts | implemented · local checks only · production blocked by default | GET /v1/facebook/profile/posts (catalog path). GET /api/v1/facebook/profile/posts. Partial owner-authorized mapping through the official Facebook Graph API Page posts edge. Requires the exact numeric Page ID to be attached to this same SignalShelf user’s Facebook Login connection; arbitrary Pages, personal profiles, visitor posts, comments, reactions, media downloads, and unsupported source fields are not returned. Requests only id, message, created_time, permalink_url, from{id,name}, and full_picture; pagination uses Meta’s opaque after cursor with a three-post page cap. Requires pages_read_engagement, Meta app review, a dedicated production gate, and written paid-use/privacy/retention clearance. Local Postman Graph simulation only; no live Meta request or app credentials. Sources: https://developers.facebook.com/docs/graph-api/reference/page/posts/ and https://developers.facebook.com/docs/permissions/. |
Profile Events | planned · not implemented · source review required | Not implemented: Meta Graph API v26.0 documents Page data access by connected-Page permissions or PPCA/PPMA, but its current Event reference says access to events on Users and Pages is available only to Facebook Marketing Partners. The current Page reference does not document an events edge, and no general profile-URL-to-events listing contract is published. Obtain Meta partner eligibility, a current versioned endpoint contract, and explicit paid-use/redistribution and retention approval; otherwise keep arbitrary profile event lookup unavailable. Sources: https://developers.facebook.com/docs/graph-api/reference/page/ and https://developers.facebook.com/docs/graph-api/reference/event/. |
Post | implemented · local checks only · production blocked by default | GET /v1/facebook/post (catalog path). GET /api/v1/facebook/post. Owner-authorized partial mapping through the official Meta Graph API. Accepts only canonical numeric Facebook Page post URLs, requires that exact Page to be connected to this SignalShelf user, and verifies the returned post author Page ID before returning the allowlisted ID, text, timestamp, permalink, Page name, and thumbnail URL. Arbitrary public posts, personal profiles, comments, reaction data, admin data, and media downloads are not returned. The current local simulation verifies same-Page isolation, field filtering, cache hits, and permission-denial refunds; Meta app approval, exact live field validation, and written paid-use/retention clearance remain outstanding, so production stays gated. Sources: https://developers.facebook.com/docs/graph-api/reference/post/ and https://developers.facebook.com/docs/permissions/. |
Transcript | planned · not implemented · source review required | Source review required before implementation: Meta requires permission for automated collection from its services. See the source gate in docs/LAUNCH.md. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
Comments | implemented · local checks only · production blocked by default | GET /v1/facebook/post/comments (catalog path). GET /api/v1/facebook/post/comments. Owner-authorized partial mapping through the Meta Graph API object comments edge. Accepts only a Page post ID in pageId_postId form or a canonical numeric Page post URL; the Page ID must match a Page connected by the same SignalShelf user. Before reading comments, it verifies the source post node resolves to that connected Page. Returns allowlisted comment ID, text, timestamp, reply count, and like count; it omits commenter identifiers and does not read arbitrary public posts. Requires pages_read_user_content, the Page MODERATE task, Meta app review, and written paid-use/privacy/retention clearance. The additional scope is requested only when FACEBOOK_PAGE_COMMENTS_SCOPE_ENABLED=true; production also requires FACEBOOK_PAGE_COMMENTS_AUTHORIZED=true. Pagination maps to the opaque Graph after cursor. Local simulation only; no Meta credentials or live request. Meta Graph docs: https://developers.facebook.com/docs/graph-api/reference/object/comments/ and https://developers.facebook.com/docs/permissions/. |
Comment Replies | implemented · local checks only · production blocked by default | GET /v1/facebook/post/comment/replies (catalog path). GET /api/v1/facebook/post/comment/replies. Owner-authorized partial mapping through Meta Graph API `/{comment-id}/comments`. The request accepts only a matching SignalShelf-signed `feedback_id` and `expansion_token` issued on a top-level comment from this caller’s own `/v1/facebook/post/comments` response; tokens are account-bound, expire after 24 hours, and cannot be imported from Scrape Creators or another service. The original comments request verifies the post belongs to the caller’s connected Page before issuing tokens. Replies use the exact connected Page token, allowlisted fields, no commenter IDs, and Graph after cursor. Requires pages_read_user_content, the Page MODERATE task, Meta app review, and written paid-use/privacy/retention clearance; production remains separately gated. Local Postman simulation only; no live Meta request. Sources: https://developers.facebook.com/docs/graph-api/reference/object/comments/ and https://developers.facebook.com/docs/permissions/. |
Facebook Group Info | planned · not implemented · source review required | Not implemented: Meta removed the Facebook Groups API and its groups_access_member_info and publish_to_groups permissions from every Graph API version on April 22, 2024. The current public Graph API contract therefore does not provide the reference operation’s arbitrary group URL/ID lookup. App review cannot restore a removed endpoint. Keep it unavailable unless Meta publishes a supported replacement or a licensed provider authorizes this exact group metadata, automated collection, paid delivery, privacy, and retention use. Do not use a logged-in browser or undocumented web endpoints. Source: https://developers.facebook.com/docs/graph-api/changelog/version19.0 and https://developers.facebook.com/legal/terms/. |
Facebook Group Posts | planned · not implemented · source review required | Not implemented: Meta removed the Facebook Groups API and its groups_access_member_info and publish_to_groups permissions from every Graph API version on April 22, 2024. No current supported public API contract establishes group post listing, sorting, or cursor pagination matching this route; app review cannot restore the removed endpoint. Keep it unavailable unless Meta publishes a supported replacement or a licensed provider authorizes this exact content, automated collection, paid delivery, privacy, retention, and deletion use. Do not use a logged-in browser or undocumented web endpoints. Source: https://developers.facebook.com/docs/graph-api/changelog/version19.0 and https://developers.facebook.com/legal/terms/. |
GitHub
| Field | Type | Description |
|---|---|---|
User | implemented · live checked · production blocked by default | GET /v1/github/user (catalog path). GET /api/v1/github/user. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The native /api/v1 GitHub route keeps the standard SignalShelf envelope; this reference-path alias additionally exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Activity and some Trending fields remain semantically different or unavailable. Live app recheck on 2026-11-02 passed for public octocat. SignalShelf deliberately omitted operator GitHub credentials, used no proxy, and charged one disposable credit. This is a point-in-time public-user sample; GitHub commercial-use review remains outstanding. GitHub ToS §H governs API data collection, bars spam uses including selling user personal information for spam, and says subscription-based API access may be offered for high-throughput use or resale of GitHub service/access. The AUP separately limits information use (regardless of API or scraping) to stated purposes, requires compliance with GitHub’s Privacy Statement, and requires personal information to be used only for the purpose authorized by the user; it prohibits reselling GitHub service or access without express written permission. These terms do not expressly classify SignalShelf’s paid API returning selected public GitHub data. Keep production gated until GitHub confirms the applicable subscription/permission covers this commercial use, privacy purpose and retention are reviewed, and the owner approves release. Trending operations also use public GitHub pages, so API terms alone do not clear those page-backed routes. Sources: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service and https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies. |
Repositories | implemented · live checked · production blocked by default | GET /v1/github/user/repositories (catalog path). GET /api/v1/github/repositories. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The native /api/v1 GitHub route keeps the standard SignalShelf envelope; this reference-path alias additionally exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Activity and some Trending fields remain semantically different or unavailable. Live app recheck on 2026-11-02 passed for public octocat and returned eight repositories for the selected page. SignalShelf deliberately omitted operator GitHub credentials, used no proxy, and charged one disposable credit. This is a page sample; GitHub commercial-use review remains outstanding. GitHub ToS §H governs API data collection, bars spam uses including selling user personal information for spam, and says subscription-based API access may be offered for high-throughput use or resale of GitHub service/access. The AUP separately limits information use (regardless of API or scraping) to stated purposes, requires compliance with GitHub’s Privacy Statement, and requires personal information to be used only for the purpose authorized by the user; it prohibits reselling GitHub service or access without express written permission. These terms do not expressly classify SignalShelf’s paid API returning selected public GitHub data. Keep production gated until GitHub confirms the applicable subscription/permission covers this commercial use, privacy purpose and retention are reviewed, and the owner approves release. Trending operations also use public GitHub pages, so API terms alone do not clear those page-backed routes. Sources: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service and https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies. |
Pull Requests | implemented · live checked · production blocked by default | GET /v1/github/user/pull-requests (catalog path). GET /api/v1/github/user-pull-requests. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The native /api/v1 GitHub route keeps the standard SignalShelf envelope; this reference-path alias additionally exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Activity and some Trending fields remain semantically different or unavailable. Live app recheck on 2026-11-02 passed for public octocat and returned eight authored pull requests for the selected page. SignalShelf deliberately omitted operator GitHub credentials, used no proxy, and charged one disposable credit. GitHub search caps results; this is not a complete archive, and commercial-use review remains outstanding. GitHub ToS §H governs API data collection, bars spam uses including selling user personal information for spam, and says subscription-based API access may be offered for high-throughput use or resale of GitHub service/access. The AUP separately limits information use (regardless of API or scraping) to stated purposes, requires compliance with GitHub’s Privacy Statement, and requires personal information to be used only for the purpose authorized by the user; it prohibits reselling GitHub service or access without express written permission. These terms do not expressly classify SignalShelf’s paid API returning selected public GitHub data. Keep production gated until GitHub confirms the applicable subscription/permission covers this commercial use, privacy purpose and retention are reviewed, and the owner approves release. Trending operations also use public GitHub pages, so API terms alone do not clear those page-backed routes. Sources: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service and https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies. |
Activity | implemented · live checked · production blocked by default | GET /v1/github/user/activity (catalog path). GET /api/v1/github/contributions. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The native /api/v1 GitHub route keeps the standard SignalShelf envelope; this reference-path alias additionally exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Activity and some Trending fields remain semantically different or unavailable. Live app recheck on 2026-11-02 passed for public octocat and returned the current public contribution-calendar month. SignalShelf deliberately omitted operator GitHub credentials, used no proxy, and charged one disposable credit. This is monthly calendar activity, not a complete event feed; GitHub commercial-use review remains outstanding. GitHub ToS §H governs API data collection, bars spam uses including selling user personal information for spam, and says subscription-based API access may be offered for high-throughput use or resale of GitHub service/access. The AUP separately limits information use (regardless of API or scraping) to stated purposes, requires compliance with GitHub’s Privacy Statement, and requires personal information to be used only for the purpose authorized by the user; it prohibits reselling GitHub service or access without express written permission. These terms do not expressly classify SignalShelf’s paid API returning selected public GitHub data. Keep production gated until GitHub confirms the applicable subscription/permission covers this commercial use, privacy purpose and retention are reviewed, and the owner approves release. Trending operations also use public GitHub pages, so API terms alone do not clear those page-backed routes. Sources: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service and https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies. |
Followers | implemented · live checked · production blocked by default | GET /v1/github/user/followers (catalog path). GET /api/v1/github/followers. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The native /api/v1 GitHub route keeps the standard SignalShelf envelope; this reference-path alias additionally exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Activity and some Trending fields remain semantically different or unavailable. Live app recheck on 2026-11-02 passed for public octocat and returned 30 followers for the selected page. SignalShelf deliberately omitted operator GitHub credentials, used no proxy, and charged one disposable credit. This is a page sample; GitHub commercial-use review remains outstanding. GitHub ToS §H governs API data collection, bars spam uses including selling user personal information for spam, and says subscription-based API access may be offered for high-throughput use or resale of GitHub service/access. The AUP separately limits information use (regardless of API or scraping) to stated purposes, requires compliance with GitHub’s Privacy Statement, and requires personal information to be used only for the purpose authorized by the user; it prohibits reselling GitHub service or access without express written permission. These terms do not expressly classify SignalShelf’s paid API returning selected public GitHub data. Keep production gated until GitHub confirms the applicable subscription/permission covers this commercial use, privacy purpose and retention are reviewed, and the owner approves release. Trending operations also use public GitHub pages, so API terms alone do not clear those page-backed routes. Sources: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service and https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies. |
Following | implemented · live checked · production blocked by default | GET /v1/github/user/following (catalog path). GET /api/v1/github/following. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The native /api/v1 GitHub route keeps the standard SignalShelf envelope; this reference-path alias additionally exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Activity and some Trending fields remain semantically different or unavailable. Live app recheck on 2026-11-02 passed for public octocat and returned nine followed accounts for the selected page. SignalShelf deliberately omitted operator GitHub credentials, used no proxy, and charged one disposable credit. This is a page sample; GitHub commercial-use review remains outstanding. GitHub ToS §H governs API data collection, bars spam uses including selling user personal information for spam, and says subscription-based API access may be offered for high-throughput use or resale of GitHub service/access. The AUP separately limits information use (regardless of API or scraping) to stated purposes, requires compliance with GitHub’s Privacy Statement, and requires personal information to be used only for the purpose authorized by the user; it prohibits reselling GitHub service or access without express written permission. These terms do not expressly classify SignalShelf’s paid API returning selected public GitHub data. Keep production gated until GitHub confirms the applicable subscription/permission covers this commercial use, privacy purpose and retention are reviewed, and the owner approves release. Trending operations also use public GitHub pages, so API terms alone do not clear those page-backed routes. Sources: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service and https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies. |
Contributions | implemented · live checked · production blocked by default | GET /v1/github/user/contributions (catalog path). GET /api/v1/github/contributions. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The native /api/v1 GitHub route keeps the standard SignalShelf envelope; this reference-path alias additionally exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Activity and some Trending fields remain semantically different or unavailable. Live app recheck on 2026-11-02 passed for public octocat and returned 365 contribution days. SignalShelf deliberately omitted operator GitHub credentials, used no proxy, and charged one disposable credit. This is a point-in-time public-calendar sample; GitHub commercial-use review remains outstanding. GitHub ToS §H governs API data collection, bars spam uses including selling user personal information for spam, and says subscription-based API access may be offered for high-throughput use or resale of GitHub service/access. The AUP separately limits information use (regardless of API or scraping) to stated purposes, requires compliance with GitHub’s Privacy Statement, and requires personal information to be used only for the purpose authorized by the user; it prohibits reselling GitHub service or access without express written permission. These terms do not expressly classify SignalShelf’s paid API returning selected public GitHub data. Keep production gated until GitHub confirms the applicable subscription/permission covers this commercial use, privacy purpose and retention are reviewed, and the owner approves release. Trending operations also use public GitHub pages, so API terms alone do not clear those page-backed routes. Sources: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service and https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies. |
Repository | implemented · live checked · production blocked by default | GET /v1/github/repository (catalog path). GET /api/v1/github/repository. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The native /api/v1 GitHub route keeps the standard SignalShelf envelope; this reference-path alias additionally exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Activity and some Trending fields remain semantically different or unavailable. Live app recheck on 2026-11-02 passed for the public octocat/Hello-World repository and confirmed it was public. SignalShelf deliberately omitted operator GitHub credentials, used no proxy, and charged one disposable credit. This is a point-in-time repository sample; commercial-use review remains outstanding. GitHub ToS §H governs API data collection, bars spam uses including selling user personal information for spam, and says subscription-based API access may be offered for high-throughput use or resale of GitHub service/access. The AUP separately limits information use (regardless of API or scraping) to stated purposes, requires compliance with GitHub’s Privacy Statement, and requires personal information to be used only for the purpose authorized by the user; it prohibits reselling GitHub service or access without express written permission. These terms do not expressly classify SignalShelf’s paid API returning selected public GitHub data. Keep production gated until GitHub confirms the applicable subscription/permission covers this commercial use, privacy purpose and retention are reviewed, and the owner approves release. Trending operations also use public GitHub pages, so API terms alone do not clear those page-backed routes. Sources: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service and https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies. |
Trending Repositories | implemented · live checked · production blocked by default | GET /v1/github/trending/repositories (catalog path). GET /api/v1/github/trending-repositories. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The native /api/v1 GitHub route keeps the standard SignalShelf envelope; this reference-path alias additionally exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Activity and some Trending fields remain semantically different or unavailable. Live app recheck on 2026-11-02 passed for GitHub public daily Trending and returned 25 repositories. SignalShelf deliberately omitted operator GitHub credentials, used no proxy, and charged one disposable credit. This is a point-in-time ranking sample; commercial-use review remains outstanding. GitHub ToS §H governs API data collection, bars spam uses including selling user personal information for spam, and says subscription-based API access may be offered for high-throughput use or resale of GitHub service/access. The AUP separately limits information use (regardless of API or scraping) to stated purposes, requires compliance with GitHub’s Privacy Statement, and requires personal information to be used only for the purpose authorized by the user; it prohibits reselling GitHub service or access without express written permission. These terms do not expressly classify SignalShelf’s paid API returning selected public GitHub data. Keep production gated until GitHub confirms the applicable subscription/permission covers this commercial use, privacy purpose and retention are reviewed, and the owner approves release. Trending operations also use public GitHub pages, so API terms alone do not clear those page-backed routes. Sources: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service and https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies. |
Trending Developers | implemented · live checked · production blocked by default | GET /v1/github/trending/developers (catalog path). GET /api/v1/github/trending-developers. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The native /api/v1 GitHub route keeps the standard SignalShelf envelope; this reference-path alias additionally exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Activity and some Trending fields remain semantically different or unavailable. Live app recheck on 2026-11-02 passed for GitHub public daily Trending and returned 25 developers. SignalShelf deliberately omitted operator GitHub credentials, used no proxy, and charged one disposable credit. This is a point-in-time ranking sample; commercial-use review remains outstanding. GitHub ToS §H governs API data collection, bars spam uses including selling user personal information for spam, and says subscription-based API access may be offered for high-throughput use or resale of GitHub service/access. The AUP separately limits information use (regardless of API or scraping) to stated purposes, requires compliance with GitHub’s Privacy Statement, and requires personal information to be used only for the purpose authorized by the user; it prohibits reselling GitHub service or access without express written permission. These terms do not expressly classify SignalShelf’s paid API returning selected public GitHub data. Keep production gated until GitHub confirms the applicable subscription/permission covers this commercial use, privacy purpose and retention are reviewed, and the owner approves release. Trending operations also use public GitHub pages, so API terms alone do not clear those page-backed routes. Sources: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service and https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies. |
Facebook Marketplace
| Field | Type | Description |
|---|---|---|
Marketplace Location Search | planned · not implemented · source review required | Source review required before implementation: Meta requires permission for automated collection from its services; verify an approved Marketplace data source and commercial-use scope before implementation. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
Marketplace Search | planned · not implemented · source review required | Source review required before implementation: Meta requires permission for automated collection from its services; verify an approved Marketplace data source and commercial-use scope before implementation. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
Marketplace Item | planned · not implemented · source review required | Source review required before implementation: Meta requires permission for automated collection from its services; verify an approved Marketplace data source and commercial-use scope before implementation. Source: https://www.facebook.com/legal/automated_data_collection_terms. |
Facebook Events
| Field | Type | Description |
|---|---|---|
Search Events | planned · not implemented · source review required | Not implemented: Meta Graph API v26.0 documents an Event object, but its current Event reference limits access to events on Users and Pages to Facebook Marketing Partners and the reviewed official documentation does not establish public keyword event search, ranking, or pagination. Do not substitute search over unrelated posts or use logged-out page extraction. Obtain written Meta partner eligibility and a documented search contract plus paid-use/redistribution and retention approval, or a licensed event-search source. Sources: https://developers.facebook.com/docs/graph-api/reference/event/ and https://developers.facebook.com/docs/graph-api/reference/page/. |
Events | planned · not implemented · source review required | Not implemented: Meta Graph API v26.0 documents Event detail data but does not establish the catalog’s URL-based event listing with today/this_week/next_week filters. Its Event reference limits access to events on Users and Pages to Facebook Marketing Partners; app events require an app token for the app that created them and group events require a group admin token plus the Groups API feature. Obtain a current matching listing contract and partner/relationship eligibility, with paid-use, retention, and redistribution approval, or keep this operation unavailable. Sources: https://developers.facebook.com/docs/graph-api/reference/event/ and https://developers.facebook.com/docs/graph-api/reference/page/. |
Event Details | planned · not implemented · source review required | Not implemented: Meta Graph API v26.0 has an Event node, but access to events on Users and Pages is limited to Facebook Marketing Partners; app-created events require that app’s access token and group events require a group admin token plus the Groups API feature. The reviewed API does not document resolving an arbitrary event URL to an ID. Obtain partner/relationship eligibility, a documented ID/URL contract, and paid-use, retention, and redistribution approval before implementation. Sources: https://developers.facebook.com/docs/graph-api/reference/event/ and https://developers.facebook.com/docs/graph-api/reference/page/. |
Facebook Ad Library
| Field | Type | Description |
|---|---|---|
Ad Details | implemented · local checks only · production blocked by default | GET /v1/facebook/adLibrary/ad (catalog path). GET /api/v1/facebook-ad-library/ad. Partial mapping through Meta’s official Ad Library API `/ads_archive` edge. Accepts a numeric ad-library ID or canonical Ad Library URL. Without country it searches political/issue ads globally; with country it supports all-ad lookup only where Meta exposes commercial ads (UK/EU). Transcripts are unavailable; only allowlisted public API fields are returned. Meta identity/location verification and an approved developer app are required. No Meta credentials or live request were used; local Graph simulation only. Retention and written paid-use clearance remain open; production stays blocked. Source: https://www.facebook.com/ads/library/api/. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Ad Transcript | planned · not implemented · source review required | Not implemented: Meta’s documented Ad Library API returns ad creative text and ad snapshot URLs, but does not document an audio/video transcript operation. Transcribing archive media would require a separately reviewed media source and permission for audio extraction and redistribution. Keep this path planned until a permitted source and commercial-use scope are established. Meta identity/location verification and approved app access are required for the available Ad Library data. Source: https://www.facebook.com/ads/library/api/. |
Search | implemented · local checks only · production blocked by default | GET /v1/facebook/adLibrary/search/ads (catalog path). GET /api/v1/facebook-ad-library/search. Partial mapping through Meta’s official Ad Library API `/ads_archive` edge. Political/issue ads are searchable globally for up to seven years; ads of any type are only returned for the UK and EU over up to one year. The adapter maps phrase/exact search, country, language, status, media type, date bounds, cursor paging, and source-backed ad/page/creative metadata. `sort_by` is rejected because this adapter has no verified equivalent. Meta identity/location verification and an approved developer app are required. No Meta credentials or live request were used; local Graph simulation only. Retention and written clearance for SignalShelf’s paid redistribution remain open; production stays blocked. Source: https://www.facebook.com/ads/library/api/. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Search | implemented · local checks only · production blocked by default | GET /v1/facebook/adLibrary/search/ads (catalog path). POST /api/v1/facebook-ad-library/search. Partial mapping through Meta’s official Ad Library API `/ads_archive` edge. Political/issue ads are searchable globally for up to seven years; ads of any type are only returned for the UK and EU over up to one year. The adapter maps phrase/exact search, country, language, status, media type, date bounds, cursor paging, and source-backed ad/page/creative metadata. `sort_by` is rejected because this adapter has no verified equivalent. Meta identity/location verification and an approved developer app are required. No Meta credentials or live request were used; local Graph simulation only. Retention and written clearance for SignalShelf’s paid redistribution remain open; production stays blocked. Source: https://www.facebook.com/ads/library/api/. |
Company Ads | implemented · local checks only · production blocked by default | GET /v1/facebook/adLibrary/company/ads (catalog path). GET /api/v1/facebook-ad-library/company/ads. Partial mapping through Meta’s official Ad Library API `/ads_archive` edge using exact numeric Facebook Page IDs. Free-text companyName, vendor sort modes, and transcripts are unsupported. Political/issue ads can be searched globally for up to seven years; ads of any type are limited to the UK/EU and one year. Meta identity/location verification and an approved developer app are required. No Meta credentials or live request were used; local Graph simulation only. Retention and written paid-use clearance remain open; production stays blocked. Source: https://www.facebook.com/ads/library/api/. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Company Ads | implemented · local checks only · production blocked by default | GET /v1/facebook/adLibrary/company/ads (catalog path). POST /api/v1/facebook-ad-library/company/ads. Partial mapping through Meta’s official Ad Library API `/ads_archive` edge using exact numeric Facebook Page IDs. Free-text companyName, vendor sort modes, and transcripts are unsupported. Political/issue ads can be searched globally for up to seven years; ads of any type are limited to the UK/EU and one year. Meta identity/location verification and an approved developer app are required. No Meta credentials or live request were used; local Graph simulation only. Retention and written paid-use clearance remain open; production stays blocked. Source: https://www.facebook.com/ads/library/api/. |
Search for Companies | planned · not implemented · source review required | Not implemented: Meta’s /ads_archive searches ad text and ads for known Page IDs, not advertiser directories. Meta’s Pages API may provide public Page search, but its official 2018 platform update says Page Public Content Access is required through app review. The current detailed endpoint contract could not be verified, so confirm current version, request/response fields, search semantics, eligibility, and approval before mapping this route. Written paid-use, caching, and retention clearance is also required. Sources: https://about.fb.com/news/2018/07/a-platform-update/, https://developers.facebook.com/documentation/pages-api/search-pages, and https://www.facebook.com/ads/library/api/. |
TikTok Ad Library
| Field | Type | Description |
|---|---|---|
Ad Library Search | implemented · local checks only · production blocked by default | GET /v1/tiktok/ad-library/search (catalog path). GET /api/v1/tiktok/ad-library/search. Uses TikTok’s official Commercial Content API Query Ads and Query Advertisers operations with research.adlib.basic. This is the separate Commercial Content API, not TikTok’s broader Research API. It searches supported EU/EEA countries over a trailing 365-day window because the source requires country and publication-date filters absent from this reference route. Supports phrase search, advertiser resolution, exact returned advertiser-ID filtering, and continuation through a query-bound source search_id. Source records/fields unavailable from TikTok are omitted; totals, spend, impressions, type, and sponsor-specific fields are not fabricated. Commercial Content API application approval is required; no credentials, approval, or live-source checks are configured. The public docs do not establish paid customer display/redistribution, caching, or retention rights for SignalShelf. Obtain written confirmation for this exact product before production. Local simulation evidence only. Sources: https://developers.tiktok.com/docs/en/commercial-content-api-query-ads, https://developers.tiktok.com/docs/en/commercial-content-api-query-advertisers, https://developers.tiktok.com/docs/en/commercial-content-api-supported-countries, and https://developers.tiktok.com/products/commercial-content-api. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Ad Library Ad | implemented · local checks only · production blocked by default | GET /v1/tiktok/ad-library/ad (catalog path). GET /api/v1/tiktok/ad-library/ad. Uses TikTok’s official Commercial Content API Get Ad Details operation with the research.adlib.basic scope and an approved server-side client token. This is the separate Commercial Content API, not TikTok’s broader Research API; TikTok requires Commercial Content API application approval and publishes an initial EU/EEA ad dataset with source-defined availability limits. The operation returns allowlisted source-backed ad, advertiser, and targeting fields; media is not downloaded, and the alias is not full response parity. No credentials, approval, or live-source check are configured. A client credential does not establish paid customer display, redistribution, caching, or retention rights; obtain written confirmation for SignalShelf’s exact use before enabling production. Sources: https://developers.tiktok.com/docs/en/commercial-content-api-get-ad-details, https://developers.tiktok.com/products/commercial-content-api, and https://developers.tiktok.com/docs/en/commercial-content-api-supported-countries. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Google Ad Library
| Field | Type | Description |
|---|---|---|
Company Ads | planned · not implemented · source review required | Not implemented: Google states that Ads Transparency Center API access is available for EEA-served ads, but the reviewed public documentation does not provide an endpoint, authentication flow, schema, or SignalShelf eligibility; access outside the EEA may be limited to regulators and self-regulatory organizations. A live read-only inspection of Google’s public BigQuery `google_political_ads` dataset confirms a political/election-only alternative: `creative_stats` exposes ad IDs/URLs, advertiser IDs/names, ad type, regions, date range, impression/spend buckets, and targeting fields, while `advertiser_stats` provides advertiser names/IDs and aggregated election counts/spend. It does not cover general commercial ads, advertiser domains, or the catalog platform filter. Dataset metadata states daily updates and deletion seven years after the election. Google Cloud’s Public Dataset docs say public tables can be integrated into applications, but Ads Transparency Center’s own terms limit use to research/information for you or your organization and prohibit generating revenue from or selling its information/content. BigQuery accessibility is not evidence of a resale exception; obtain a written license expressly covering SignalShelf’s paid API and redistribution before implementing even a political-only partial. Do not return sensitive age/gender/geo-targeting fields. No BigQuery query was run. Sources: https://support.google.com/adspolicy/answer/13733850, https://adstransparency.google.com/terms, https://docs.cloud.google.com/bigquery/public-data, and https://cloud.google.com/blog/topics/developers-practitioners/how-get-started-political-ads-transparency-report-dataset. |
Ad Details | planned · not implemented · source review required | Not implemented: Google has no documented public Ads Transparency Center search/detail endpoint in the reviewed developer docs; its Ads Transparency help page describes EEA data access but not a request contract. The public `google_political_ads.creative_stats` BigQuery table contains election-ad ID and Google report URL plus advertiser, format, region, date, and bucketed metrics, but no ad creative payload and no general commercial ads. Dataset metadata specifies daily updates and removes election data seven years after the election. Google Cloud’s Public Dataset docs allow public tables to be integrated into applications, but Ads Transparency Center’s own terms limit use to research/information for you or your organization and prohibit generating revenue from or selling its information/content. BigQuery accessibility is not evidence of a resale exception; obtain a written license expressly covering SignalShelf’s paid API and redistribution before implementing a political-ad link/metadata partial. No query or ad content retrieval was performed. Sources: https://support.google.com/adspolicy/answer/13733850, https://adstransparency.google.com/terms, https://docs.cloud.google.com/bigquery/public-data, and https://cloud.google.com/blog/topics/developers-practitioners/how-get-started-political-ads-transparency-report-dataset. |
Advertiser Search | planned · not implemented · source review required | Not implemented: Google’s Ads Transparency Center terms limit use to research or information for you/your organization and prohibit generating revenue from or selling any part of the Center or its information/content. The Center is searchable by advertiser or website name and Google states EEA API access exists, but this product is not authorized to resell the results and the reviewed materials do not publish a public versioned API contract. Google’s public BigQuery political-ad dataset is a separate narrow lead, not general advertiser/domain search; its dataset-specific paid redistribution rights remain unverified. Do not implement either source for SignalShelf’s paid API absent an express written exception/license. BigQuery query costs can apply beyond the monthly free tier. No query or undocumented browser/RPC request was run. Sources: https://adstransparency.google.com/terms, https://support.google.com/adspolicy/answer/13733850, https://docs.cloud.google.com/bigquery/public-data, and https://cloud.google.com/blog/topics/developers-practitioners/how-get-started-political-ads-transparency-report-dataset. |
LinkedIn Ad Library
| Field | Type | Description |
|---|---|---|
Search Ads | planned · not implemented · source review required | Not implemented: LinkedIn provides a public Ad Library and an external Ad Library API by developer-product request, but access is reviewed and LinkedIn API terms prohibit distributing standalone APIs or selling access to aggregated LinkedIn content without applicable authorization. Obtain written approval for SignalShelf’s paid distribution and confirm the allowed scope first. |
Ad Details | planned · not implemented · source review required | Not implemented: LinkedIn provides a public Ad Library and an external Ad Library API by developer-product request, but access is reviewed and LinkedIn API terms prohibit distributing standalone APIs or selling access to aggregated LinkedIn content without applicable authorization. Obtain written approval for SignalShelf’s paid distribution and confirm the allowed scope first. |
| Field | Type | Description |
|---|---|---|
Search Posts | planned · not implemented · source review required | Not implemented: X’s current Developer Policy generally allows third-party redistribution of X Content only as Post IDs, Direct Message IDs, and/or User IDs. It allows up to 500 public Post Objects and/or User Objects per person per day only through non-automated delivery (such as spreadsheets or PDFs), not SignalShelf’s customer API. The policy also bars using X API to measure X for competitive/commercial benchmarking and requires displayed Posts to be current, with unavailable content removed promptly (including within 24 hours of a removal request where applicable). SignalShelf needs written X approval or a license expressly covering automated full-object distribution and this paid creator-research use before implementing or making requests. The current API is pay-per-use, so approved field/endpoint costs and spend caps need review. Source: https://docs.x.com/developer-terms/policy. |
Profile | planned · not implemented · source review required | Not implemented: X’s current Developer Policy generally allows third-party redistribution of X Content only as Post IDs, Direct Message IDs, and/or User IDs. It allows up to 500 public Post Objects and/or User Objects per person per day only through non-automated delivery (such as spreadsheets or PDFs), not SignalShelf’s customer API. The policy also bars using X API to measure X for competitive/commercial benchmarking and requires displayed Posts to be current, with unavailable content removed promptly (including within 24 hours of a removal request where applicable). SignalShelf needs written X approval or a license expressly covering automated full-object distribution and this paid creator-research use before implementing or making requests. The current API is pay-per-use, so approved field/endpoint costs and spend caps need review. Source: https://docs.x.com/developer-terms/policy. |
User Tweets | planned · not implemented · source review required | Not implemented: X’s current Developer Policy generally allows third-party redistribution of X Content only as Post IDs, Direct Message IDs, and/or User IDs. It allows up to 500 public Post Objects and/or User Objects per person per day only through non-automated delivery (such as spreadsheets or PDFs), not SignalShelf’s customer API. The policy also bars using X API to measure X for competitive/commercial benchmarking and requires displayed Posts to be current, with unavailable content removed promptly (including within 24 hours of a removal request where applicable). SignalShelf needs written X approval or a license expressly covering automated full-object distribution and this paid creator-research use before implementing or making requests. The current API is pay-per-use, so approved field/endpoint costs and spend caps need review. Source: https://docs.x.com/developer-terms/policy. |
Tweet Details | planned · not implemented · source review required | Not implemented: X’s current Developer Policy generally allows third-party redistribution of X Content only as Post IDs, Direct Message IDs, and/or User IDs. It allows up to 500 public Post Objects and/or User Objects per person per day only through non-automated delivery (such as spreadsheets or PDFs), not SignalShelf’s customer API. The policy also bars using X API to measure X for competitive/commercial benchmarking and requires displayed Posts to be current, with unavailable content removed promptly (including within 24 hours of a removal request where applicable). SignalShelf needs written X approval or a license expressly covering automated full-object distribution and this paid creator-research use before implementing or making requests. The current API is pay-per-use, so approved field/endpoint costs and spend caps need review. Source: https://docs.x.com/developer-terms/policy. |
Transcript | planned · not implemented · source review required | Not implemented: X’s current Developer Policy generally allows third-party redistribution of X Content only as Post IDs, Direct Message IDs, and/or User IDs. It allows up to 500 public Post Objects and/or User Objects per person per day only through non-automated delivery (such as spreadsheets or PDFs), not SignalShelf’s customer API. The policy also bars using X API to measure X for competitive/commercial benchmarking and requires displayed Posts to be current, with unavailable content removed promptly (including within 24 hours of a removal request where applicable). SignalShelf needs written X approval or a license expressly covering automated full-object distribution and this paid creator-research use before implementing or making requests. The current API is pay-per-use, so approved field/endpoint costs and spend caps need review. Source: https://docs.x.com/developer-terms/policy. |
Community | planned · not implemented · source review required | Not implemented: X’s current Developer Policy generally allows third-party redistribution of X Content only as Post IDs, Direct Message IDs, and/or User IDs. It allows up to 500 public Post Objects and/or User Objects per person per day only through non-automated delivery (such as spreadsheets or PDFs), not SignalShelf’s customer API. The policy also bars using X API to measure X for competitive/commercial benchmarking and requires displayed Posts to be current, with unavailable content removed promptly (including within 24 hours of a removal request where applicable). SignalShelf needs written X approval or a license expressly covering automated full-object distribution and this paid creator-research use before implementing or making requests. The current API is pay-per-use, so approved field/endpoint costs and spend caps need review. Source: https://docs.x.com/developer-terms/policy. |
Community Tweets | planned · not implemented · source review required | Not implemented: X’s current Developer Policy generally allows third-party redistribution of X Content only as Post IDs, Direct Message IDs, and/or User IDs. It allows up to 500 public Post Objects and/or User Objects per person per day only through non-automated delivery (such as spreadsheets or PDFs), not SignalShelf’s customer API. The policy also bars using X API to measure X for competitive/commercial benchmarking and requires displayed Posts to be current, with unavailable content removed promptly (including within 24 hours of a removal request where applicable). SignalShelf needs written X approval or a license expressly covering automated full-object distribution and this paid creator-research use before implementing or making requests. The current API is pay-per-use, so approved field/endpoint costs and spend caps need review. Source: https://docs.x.com/developer-terms/policy. |
| Field | Type | Description |
|---|---|---|
Subreddit Details | implemented · local checks only · production blocked by default | GET /v1/reddit/subreddit/details (catalog path). GET /api/v1/reddit/subreddit/details. Partial public-data mapping through the documented Reddit OAuth Data API, with allowlisted fields, source cursors, and no persistent cache. No private/quarantined access, browser/proxy fallback, transcript extraction, or fabricated fields. Local HTTP simulation only; no Reddit credentials or live calls. Production is blocked until Reddit's written commercial agreement explicitly authorizes SignalShelf's paid API and redistribution. Source: https://redditinc.com/policies/data-api-terms and https://www.reddit.com/dev/api/oauth/. |
Subreddit Posts | implemented · local checks only · production blocked by default | GET /v1/reddit/subreddit (catalog path). GET /api/v1/reddit/subreddit. Partial public-data mapping through the documented Reddit OAuth Data API, with allowlisted fields, source cursors, and no persistent cache. No private/quarantined access, browser/proxy fallback, transcript extraction, or fabricated fields. Local HTTP simulation only; no Reddit credentials or live calls. Production is blocked until Reddit's written commercial agreement explicitly authorizes SignalShelf's paid API and redistribution. Source: https://redditinc.com/policies/data-api-terms and https://www.reddit.com/dev/api/oauth/. |
Subreddit Search | implemented · local checks only · production blocked by default | GET /v1/reddit/subreddit/search (catalog path). GET /api/v1/reddit/subreddit/search. Partial public-data mapping through the documented Reddit OAuth Data API, with allowlisted fields, source cursors, and no persistent cache. No private/quarantined access, browser/proxy fallback, transcript extraction, or fabricated fields. Local HTTP simulation only; no Reddit credentials or live calls. Production is blocked until Reddit's written commercial agreement explicitly authorizes SignalShelf's paid API and redistribution. Source: https://redditinc.com/policies/data-api-terms and https://www.reddit.com/dev/api/oauth/. |
Post | implemented · local checks only · production blocked by default | GET /v1/reddit/post (catalog path). GET /api/v1/reddit/post. Partial public-data mapping through the documented Reddit OAuth Data API, with allowlisted fields, source cursors, and no persistent cache. No private/quarantined access, browser/proxy fallback, transcript extraction, or fabricated fields. Local HTTP simulation only; no Reddit credentials or live calls. Production is blocked until Reddit's written commercial agreement explicitly authorizes SignalShelf's paid API and redistribution. Source: https://redditinc.com/policies/data-api-terms and https://www.reddit.com/dev/api/oauth/. |
Post Comments | implemented · local checks only · production blocked by default | GET /v1/reddit/post/comments (catalog path). GET /api/v1/reddit/post/comments. Partial public-data mapping through the documented Reddit OAuth Data API, with allowlisted fields, source cursors, and no persistent cache. No private/quarantined access, browser/proxy fallback, transcript extraction, or fabricated fields. Local HTTP simulation only; no Reddit credentials or live calls. Production is blocked until Reddit's written commercial agreement explicitly authorizes SignalShelf's paid API and redistribution. Source: https://redditinc.com/policies/data-api-terms and https://www.reddit.com/dev/api/oauth/. |
Post Comments | implemented · local checks only · production blocked by default | GET /v1/reddit/post/comments (catalog path). POST /api/v1/reddit/post/comments. Partial public-data mapping through the documented Reddit OAuth Data API, with allowlisted fields, source cursors, and no persistent cache. No private/quarantined access, browser/proxy fallback, transcript extraction, or fabricated fields. Local HTTP simulation only; no Reddit credentials or live calls. Production is blocked until Reddit's written commercial agreement explicitly authorizes SignalShelf's paid API and redistribution. Source: https://redditinc.com/policies/data-api-terms and https://www.reddit.com/dev/api/oauth/. |
Post Transcript | planned · not implemented · source review required | Not implemented: Reddit’s Data API documents posts, comments, and subreddit data, but no official transcript endpoint for arbitrary video posts was identified. A Reddit Data API commercial agreement would not by itself authorize obtaining/transcribing post video media or redistributing generated transcripts. Revisit only with written Reddit approval for the media source and transcript use plus a transcription/retention license. Use only Reddit-provided credentials and identify SignalShelf accurately; do not scrape pages or mask request identity. Sources: https://redditinc.com/policies/data-api-terms and https://www.reddit.com/dev/api/. |
Search | implemented · local checks only · production blocked by default | GET /v1/reddit/search (catalog path). GET /api/v1/reddit/search. Partial public-data mapping through the documented Reddit OAuth Data API, with allowlisted fields, source cursors, and no persistent cache. No private/quarantined access, browser/proxy fallback, transcript extraction, or fabricated fields. Local HTTP simulation only; no Reddit credentials or live calls. Production is blocked until Reddit's written commercial agreement explicitly authorizes SignalShelf's paid API and redistribution. Source: https://redditinc.com/policies/data-api-terms and https://www.reddit.com/dev/api/oauth/. |
Search Ads | planned · not implemented · source review required | Source review required before implementation: Reddit Data API access requires approval and commercial use requires a separate agreement. The aggregate OpenAPI omits some Reddit routes; endpoint-specific OpenAPI files confirm their request contracts, but that does not authorize collection or commercial use. Obtain written authorization before implementation. Sources: https://support.reddithelp.com/hc/en-us/articles/14945211791892-Developer-Platform-Accessing-Reddit-Data and https://redditinc.com/policies/data-api-terms. |
Get Ad | planned · not implemented · source review required | Source review required before implementation: Reddit Data API access requires approval and commercial use requires a separate agreement. The aggregate OpenAPI omits some Reddit routes; endpoint-specific OpenAPI files confirm their request contracts, but that does not authorize collection or commercial use. Obtain written authorization before implementation. Sources: https://support.reddithelp.com/hc/en-us/articles/14945211791892-Developer-Platform-Accessing-Reddit-Data and https://redditinc.com/policies/data-api-terms. |
Truth Social
| Field | Type | Description |
|---|---|---|
Profile | planned · not implemented · source review required | Not implemented: Truth Social Terms prohibit automated/non-human access and systematic database collection without written permission, and restrict commercial use/distribution absent express prior written permission. TMTG reported that its Truth API launched on August 1, 2026 as a licensed B2B subscription feed for posts from certain top accounts. No public developer contract, self-serve credentials, arbitrary profile/post lookup, or full-catalog coverage is documented in the reviewed material. Request a written license and exact API scope before implementation; do not use automated site access as a substitute. Sources: https://help.truthsocial.com/legal/terms-of-service/ and https://www.sec.gov/Archives/edgar/data/1849635/000143774926026777/djt20260630_10q.htm. |
User Posts | planned · not implemented · source review required | Not implemented: Truth Social Terms prohibit automated/non-human access and systematic database collection without written permission, and restrict commercial use/distribution absent express prior written permission. TMTG reported that its Truth API launched on August 1, 2026 as a licensed B2B subscription feed for posts from certain top accounts. No public developer contract, self-serve credentials, arbitrary profile/post lookup, or full-catalog coverage is documented in the reviewed material. Request a written license and exact API scope before implementation; do not use automated site access as a substitute. Sources: https://help.truthsocial.com/legal/terms-of-service/ and https://www.sec.gov/Archives/edgar/data/1849635/000143774926026777/djt20260630_10q.htm. |
Post | planned · not implemented · source review required | Not implemented: Truth Social Terms prohibit automated/non-human access and systematic database collection without written permission, and restrict commercial use/distribution absent express prior written permission. TMTG reported that its Truth API launched on August 1, 2026 as a licensed B2B subscription feed for posts from certain top accounts. No public developer contract, self-serve credentials, arbitrary profile/post lookup, or full-catalog coverage is documented in the reviewed material. Request a written license and exact API scope before implementation; do not use automated site access as a substitute. Sources: https://help.truthsocial.com/legal/terms-of-service/ and https://www.sec.gov/Archives/edgar/data/1849635/000143774926026777/djt20260630_10q.htm. |
Threads
| Field | Type | Description |
|---|---|---|
Profile | implemented · local checks only · production blocked by default | GET /v1/threads/profile (catalog path). GET /api/v1/threads/profile. Uses Meta’s official OAuth-protected Threads profile_lookup endpoint for exact public usernames. Only allowlisted public profile fields are returned. Local Postman simulation checks cover request mapping and app authentication; no Meta app credentials or live-source check are configured. Meta app approval and written clearance for paid redistribution are required before production. The native /api/v1 Threads route keeps the standard SignalShelf envelope; this reference path additionally exposes reference-named public fields and SignalShelf credit values alongside data/meta. Exact response parity is partial. Private profiles and viewer relationship fields are excluded; Meta app approval and written commercial-use clearance are required before production. |
Posts | implemented · local checks only · production blocked by default | GET /v1/threads/user/posts (catalog path). GET /api/v1/threads/posts. Uses Meta’s official OAuth-protected profile_posts endpoint and returns allowlisted public post fields with source pagination. Private profiles, viewer relationship fields, and media downloads are not supported. Local Postman simulation checks only; no live credentials. Meta app approval and written clearance for paid redistribution are required before production. The native /api/v1 Threads route keeps the standard SignalShelf envelope; this reference path additionally exposes reference-named public fields and SignalShelf credit values alongside data/meta. Exact response parity is partial. Private profiles and viewer relationship fields are excluded; Meta app approval and written commercial-use clearance are required before production. |
Post | implemented · local checks only · production blocked by default | GET /v1/threads/post (catalog path). GET /api/v1/threads/post-by-url. Partial official-source mapping. Parses a canonical public Threads URL, reads Meta’s OAuth-protected public profile_posts feed for the URL handle, and returns the matching source post by shortcode after searching up to three pages/300 records. Requires an approved Meta Threads app token and any permissions Meta applies to profile discovery. Comments, author continuations, related-post recommendations, complete post history, and private/inaccessible posts are not returned. Cache ages above seven days are capped to seven days. Local simulation only; no Meta app credentials or live post-detail check. App approval, field validation, retention and written paid-redistribution clearance remain outstanding; production stays source-gated. Source: https://www.postman.com/meta/threads/documentation/dht3nzz/threads-api. The native /api/v1 Threads route keeps the standard SignalShelf envelope; this reference path additionally exposes reference-named public fields and SignalShelf credit values alongside data/meta. Exact response parity is partial. Private profiles and viewer relationship fields are excluded; Meta app approval and written commercial-use clearance are required before production. Meta also provides an official Threads oEmbed endpoint for public post URLs for embed use (documented by Meta’s official WordPress embed plugin). A point-in-time unauthenticated check returned only `type`, `version`, `html`, `provider_name`, `provider_url`, and `width`; the HTML is embed markup, not the structured post/comments/relatedPosts/threadItems response in this catalog operation. This does not establish permission to repurpose oEmbed as a paid data API. Keep this operation planned pending a source that matches its contract and written commercial-use clearance. Source: https://github.com/facebook/meta-embeds-for-wordpress. |
Search by Keyword | implemented · local checks only · production blocked by default | GET /v1/threads/search (catalog path). GET /api/v1/threads/search. Uses Meta’s official OAuth-protected keyword_search endpoint for public post keyword or tag search, including source-side ranking, date bounds, and pagination. This is post search, not general user search. Local Postman simulation checks only; no live credentials. Meta app approval and written clearance for paid redistribution are required before production. The native /api/v1 Threads route keeps the standard SignalShelf envelope; this reference path additionally exposes reference-named public fields and SignalShelf credit values alongside data/meta. Exact response parity is partial. Private profiles and viewer relationship fields are excluded; Meta app approval and written commercial-use clearance are required before production. |
Search Users | implemented · local checks only · production blocked by default | GET /v1/threads/search/users (catalog path). GET /api/v1/threads/search-users. Partial mapping only: the reference query is treated as one exact public Threads username, resolved through Meta’s official OAuth-protected profile_lookup endpoint with threads_profile_discovery. The official API does not provide broad name or username search through this operation, so multiword/broad queries are rejected. Local Postman simulation checks only; no Meta app credentials or live source check. App approval and written paid-use clearance are required before production. Source: https://www.postman.com/meta/threads/request/34203612-d5ea7186-5329-4c76-bbb6-3dd408e508b5 |
Bluesky
| Field | Type | Description |
|---|---|---|
Profile | implemented · live checked · production blocked by default | GET /v1/bluesky/profile (catalog path). GET /api/v1/bluesky/profile. Uses Bluesky’s official public AppView profile endpoint without an account token. Live app verification passed for bsky.app by handle and DID on 2026-11-02; handle case is normalized and cacheable across accounts. This is the upstream public profile object in SignalShelf’s resource wrapper, not an exact Scrape Creators response. The native /api/v1 Bluesky route keeps the standard SignalShelf envelope; this reference-path alias exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Latest live app check on 2026-11-03 passed for bsky.app profile lookup by handle and DID. The run also passed all five public author-feed filters, cursor continuation to a distinct page, cache hits, and canonical post detail with 78 depth-one replies and no truncation. Twelve fresh disposable local credits; no proxy or provider credential. The latest check was recorded at 07:21 UTC. This is point-in-time evidence, not an uptime or commercial-use guarantee. |
Posts | implemented · live checked · production blocked by default | GET /v1/bluesky/user/posts (catalog path). GET /api/v1/bluesky/posts. Uses Bluesky’s recommended cached public AppView author-feed endpoint without an account token; its documentation says most app.bsky GETs are public and unauthenticated. Accepts a public handle or DID via user_id, validated against the live AppView. Supports SignalShelf-only limit/cursor/filter extensions beyond the reference contract; all five documented filter values and distinct cursor pages passed live checks. On 2026-11-02, a fresh live app check returned 30 posts and five distinct filtered-feed samples (4–5 items each); cache reuse and distinct continuation pages passed. On 2026-11-03, the same checks passed again with 30 feed items, filter counts 5/5/5/4/5, distinct continuation records, and cache reuse. Verification established accepted parameters and response shape for bsky.app, not feed-wide filter completeness. Returns a SignalShelf resource wrapper rather than an exact Scrape Creators response shape. The native /api/v1 Bluesky route keeps the standard SignalShelf envelope; this reference-path alias exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Bluesky’s current Terms say users retain ownership of their content and do not state a blanket license for a separately sold third-party data API; its Network Services Privacy Notice says third-party developers control their own privacy practices. These documents do not establish that SignalShelf may commercially redistribute or retain this data on its proposed terms. Production remains gated pending rights, privacy, and retention review or written clearance. Sources: https://bsky.network/docs/bluesky-api/request-proxying/, https://bsky.network/docs/rate-limits/, https://bsky.social/about/support/tos, https://bsky.social/about/support/network-services-privacy-policy. The native /api/v1 Bluesky route keeps the standard SignalShelf envelope; this reference-path alias exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. |
Post | implemented · live checked · production blocked by default | GET /v1/bluesky/post (catalog path). GET /api/v1/bluesky/post. Uses Bluesky’s recommended cached public AppView post/thread endpoints without an account token; its documentation says most app.bsky GETs are public and unauthenticated. Accepts the canonical public post URL; the existing handle+rkey form remains an alias and shares the same normalized cache key. Live URL lookup passed through the authenticated app and preserves source-provided threadContext. On 2026-11-02, one public bsky.app thread returned 73 direct replies. On 2026-11-03, the canonical post route returned 78 direct replies with no truncation in the latest live batch at 07:21 UTC. Compared with the saved reference audit shape, public leaf replies may omit a child-replies array and reply posts may omit optional embed fields; these fields are not fabricated. Up to 100 replies from one thread level are returned; deeper replies are not fetched. The native /api/v1 Bluesky route keeps the standard SignalShelf envelope; this reference-path alias exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Bluesky’s current Terms say users retain ownership of their content and do not state a blanket license for a separately sold third-party data API; its Network Services Privacy Notice says third-party developers control their own privacy practices. These documents do not establish that SignalShelf may commercially redistribute or retain this data on its proposed terms. Production remains gated pending rights, privacy, and retention review or written clearance. Sources: https://bsky.network/docs/bluesky-api/request-proxying/, https://bsky.network/docs/rate-limits/, https://bsky.social/about/support/tos, https://bsky.social/about/support/network-services-privacy-policy. The native /api/v1 Bluesky route keeps the standard SignalShelf envelope; this reference-path alias exposes reference-named top-level fields, success, and SignalShelf account credit values alongside data/meta. Post details include up to 100 publicly indexed replies from one level of the official thread response; deeper replies may be omitted. |
| Field | Type | Description |
|---|---|---|
Search | planned · not implemented · source review required | Not implemented: the reviewed Pinterest API documentation does not establish an unrestricted public search contract matching this catalog operation. Pinterest Developer Guidelines prohibit competitor research/benchmarking without express written authorization and prohibit sharing or selling API information; their default terms also restrict storage of data obtained through Materials except limited account analytics. Do not use owner OAuth, public pages, or the API to offer a third-party creator-search product without written Pinterest authorization covering search, storage, and paid redistribution. Sources: https://developers.pinterest.com/terms/ and https://developers.pinterest.com/docs/api/v5/introduction/. |
Pin | planned · not implemented · source review required | Not implemented: Pinterest API v5 supports authenticated Pin operations, but the reviewed contract does not establish arbitrary third-party Pin lookup with rights for SignalShelf to store or resell its fields. Developer Guidelines prohibit sharing or selling API information and require explicit written authorization for competitor research/benchmarking; default storage is restricted. A user-connected Pin operation is not public creator-research parity. Sources: https://developers.pinterest.com/docs/work-with-organic-content-and-users/create-boards-and-pins/ and https://developers.pinterest.com/terms/. |
User Boards | planned · not implemented · source review required | Not implemented: Pinterest API v5 can list boards for the token’s authorized user with `boards:read`, but Pinterest Developer Guidelines limit data use to approved purposes, restrict storage, and prohibit sharing or selling API information. This own-account operation cannot power SignalShelf’s third-party public creator database or paid resale without express written Pinterest authorization. Sources: https://developers.pinterest.com/docs/work-with-organic-content-and-users/create-boards-and-pins/ and https://developers.pinterest.com/terms/. |
Topic | planned · not implemented · source review required | Not implemented: the reviewed Pinterest API docs do not establish a public topic lookup contract equivalent to this catalog operation. Pinterest Developer Guidelines also prohibit competitor research/benchmarking without express written authorization and prohibit sharing or selling API information. Obtain written scope for topic discovery, storage, and paid redistribution before implementation. Sources: https://developers.pinterest.com/docs/api/v5/introduction/ and https://developers.pinterest.com/terms/. |
Board | planned · not implemented · source review required | Not implemented: Pinterest API v5 board detail is available only under its OAuth/API access model and is subject to Pinner data-access checks. The reviewed terms do not authorize SignalShelf to turn account-scoped board data into a stored/resold third-party research API; written authorization is required for competitor research, sharing, or sale. Sources: https://developers.pinterest.com/docs/work-with-organic-content-and-users/create-boards-and-pins/ and https://developers.pinterest.com/terms/. |
| Field | Type | Description |
|---|---|---|
Search | planned · not implemented · source review required | Not implemented: Google Custom Search JSON API is closed to new customers and Google says the service ends January 1, 2027. Vertex AI Search is the suggested alternative for up to 50 domains, not equivalent full-web search. Do not build this catalog operation against a discontinued service. |
Twitch
| Field | Type | Description |
|---|---|---|
Profile | implemented · live checked · production blocked by default | GET /v1/twitch/profile (catalog path). GET /v1/twitch/profile. Reference GET alias accepts a public channel handle and maps Twitch logged-out profile fields. A live app check against shroud validated the alias and a zero-credit cache hit; this is one public profile sample. Production is source-gated pending written clearance. Production live access is disabled by default: Twitch's Developer Services Agreement bars selling, licensing or redistributing API metadata absent a separate written agreement. |
User Videos | implemented · local checks only · production blocked by default | GET /v1/twitch/user/videos (catalog path). GET /api/v1/twitch/user/videos. Uses official Twitch Helix Get Users, Get Streams, and Get Videos with an operator app access token. Maps source-backed public channel details, live status, current viewer count, video metadata, stream ID, viewability, and muted segments when returned. Supports the catalog type filters and Helix cursor paging, plus source-side time/views/trending sorting, language, and publication-period filters. Sorting and filters apply to the source result before pagination; retrieving a complete channel history still requires paging. Follower counts and social links are omitted because Helix does not provide them in these responses. Local mocked app checks passed; no live credentials are configured. Written commercial redistribution approval is still required before production. Production live access remains blocked by the Twitch commercial-use gate. |
User Schedule | implemented · live checked · production blocked by default | GET /v1/twitch/user/schedule (catalog path). GET /api/v1/twitch/user/schedule. Maps public Twitch iCalendar events to reference-style schedule segments, preserving only source-backed identifiers, titles, times, timezone, recurrence, description, URL, cancellation and location. On 2026-11-03, the authenticated app returned six public shroud events through the native and reference routes; the alias reused cache at zero extra credits. It does not synthesize schedule IDs, reminders, categories, videos, or stream state. This is a point-in-time source check only; commercial source clearance remains required. The reference path is accepted as an alias; authentication and SignalShelf account-scoped data apply. |
Clip Transcript | planned · not implemented · source review required | Not implemented: Twitch Helix documents clip metadata and temporary clip-download URLs, but no transcript endpoint. Clip downloads require a user access token with editor:manage:clips or channel:manage:clips and matching editor/broadcaster IDs; this download scope does not itself grant transcript or paid redistribution rights. SignalShelf has no approved Twitch clip-download/transcription flow. Revisit only after written Twitch commercial permission, an authorized clip-access model, and a transcription/retention contract are established. Sources: https://dev.twitch.tv/docs/api/reference/ and https://dev.twitch.tv/docs/api/clips/. Production live access is disabled by default: Twitch's Developer Services Agreement bars selling, licensing or redistributing API metadata absent a separate written agreement. |
Clip | implemented · local checks only · production blocked by default | GET /v1/twitch/clip (catalog path). GET /api/v1/twitch/clip. Uses official Twitch Helix Get Clips by a public clip URL slug. Maps Helix metadata, embed URL and thumbnail URL; it does not fetch downloadable media assets or transcripts, so the richer vendor asset list is unavailable. Cache age is capped at seven days. Local mocked app checks passed, but no live credentials are configured. Written commercial redistribution approval is still required before production. Production live access remains blocked by the Twitch commercial-use gate. |
Apple Music
| Field | Type | Description |
|---|---|---|
Artist | implemented · live checked · production blocked by default | GET /v1/apple-music/artist (catalog path). GET /api/v1/apple-music/artist. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The reference alias was live-checked against Apple iTunes Search/Lookup through SignalShelf and reuses the native cache without an extra debit. It exposes available public catalog fields plus SignalShelf data/meta; editorial notes, Apple Music API-only fields, previews/artwork, larger related-item sets, and unsupported entity types remain unavailable. Mapping is partial and commercial source clearance is required. Latest authenticated app check on 2026-11-03 returned HTTP 200 for the US storefront: one artist, 12 albums, 24 top songs, and 12 music videos. The reference alias matched the native response via a free cache hit; one disposable fresh credit was charged. Apple Search API commercial display/reuse review remains outstanding. |
Album | implemented · live checked · production blocked by default | GET /v1/apple-music/album (catalog path). GET /api/v1/apple-music/album. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The reference alias was live-checked against Apple iTunes Search/Lookup through SignalShelf and reuses the native cache without an extra debit. It exposes available public catalog fields plus SignalShelf data/meta; editorial notes, Apple Music API-only fields, previews/artwork, larger related-item sets, and unsupported entity types remain unavailable. Mapping is partial and commercial source clearance is required. Latest authenticated app check on 2026-11-03 returned HTTP 200 for a public US-storefront album; the reference alias matched the native response via a free cache hit. One disposable fresh credit was charged. Apple Search API commercial display/reuse review remains outstanding. |
Track | implemented · live checked · production blocked by default | GET /v1/apple-music/track (catalog path). GET /api/v1/apple-music/track. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The reference alias was live-checked against Apple iTunes Search/Lookup through SignalShelf and reuses the native cache without an extra debit. It exposes available public catalog fields plus SignalShelf data/meta; editorial notes, Apple Music API-only fields, previews/artwork, larger related-item sets, and unsupported entity types remain unavailable. Mapping is partial and commercial source clearance is required. Latest authenticated app check on 2026-11-03 returned HTTP 200 for a public US-storefront track; the reference alias matched the native response via a free cache hit. One disposable fresh credit was charged. Apple Search API commercial display/reuse review remains outstanding. |
Search | implemented · live checked · production blocked by default | GET /v1/apple-music/search (catalog path). GET /api/v1/apple-music/search. Maps to an existing SignalShelf resource route. Request fields, response shape, pagination, data availability, source restrictions, and commercial use are documented as operation-specific limits; this alias does not imply exact parity. The reference alias was live-checked against Apple iTunes Search/Lookup through SignalShelf and reuses the native cache without an extra debit. It exposes available public catalog fields plus SignalShelf data/meta; editorial notes, Apple Music API-only fields, previews/artwork, larger related-item sets, and unsupported entity types remain unavailable. Mapping is partial and commercial source clearance is required. Latest authenticated app check on 2026-11-03 returned HTTP 200 for public US-storefront search with 50 results; the reference alias matched the native response via a free cache hit. One disposable fresh credit was charged. Apple Search API commercial display/reuse review remains outstanding. |
Spotify
| Field | Type | Description |
|---|---|---|
Artist | planned · not implemented · source review required | Not implemented: Spotify’s Developer Policy prohibits offering Spotify metadata, cover art, or audio previews as a standalone service/product and prohibits analyzing Spotify content/service for derived listenership metrics, benchmarking, user metrics, or user profiling. Display requires Spotify attribution/marks and a link to the matching content. SignalShelf’s paid standalone API therefore needs written Spotify permission or a separate license before implementation or API calls. Current contract limitations also differ from older examples: since the 2026 Web API changes, artist follower/popularity fields and artist top tracks are unavailable; search accepts at most 10 results per request; playlist item contents are returned only for playlists the user owns or collaborates on. Development Mode additionally requires the app owner to have Premium and limits new apps to one client ID and five users. No Spotify API request or live check was made. Sources: https://developer.spotify.com/policy (II.4, III.13), https://developer.spotify.com/documentation/web-api/tutorials/february-2026-migration-guide, and https://developer.spotify.com/documentation/web-api/concepts/quota-modes. |
Track | planned · not implemented · source review required | Not implemented: Spotify’s Developer Policy prohibits offering Spotify metadata, cover art, or audio previews as a standalone service/product and prohibits analyzing Spotify content/service for derived listenership metrics, benchmarking, user metrics, or user profiling. Display requires Spotify attribution/marks and a link to the matching content. SignalShelf’s paid standalone API therefore needs written Spotify permission or a separate license before implementation or API calls. Current contract limitations also differ from older examples: since the 2026 Web API changes, artist follower/popularity fields and artist top tracks are unavailable; search accepts at most 10 results per request; playlist item contents are returned only for playlists the user owns or collaborates on. Development Mode additionally requires the app owner to have Premium and limits new apps to one client ID and five users. No Spotify API request or live check was made. Sources: https://developer.spotify.com/policy (II.4, III.13), https://developer.spotify.com/documentation/web-api/tutorials/february-2026-migration-guide, and https://developer.spotify.com/documentation/web-api/concepts/quota-modes. |
Album | planned · not implemented · source review required | Not implemented: Spotify’s Developer Policy prohibits offering Spotify metadata, cover art, or audio previews as a standalone service/product and prohibits analyzing Spotify content/service for derived listenership metrics, benchmarking, user metrics, or user profiling. Display requires Spotify attribution/marks and a link to the matching content. SignalShelf’s paid standalone API therefore needs written Spotify permission or a separate license before implementation or API calls. Current contract limitations also differ from older examples: since the 2026 Web API changes, artist follower/popularity fields and artist top tracks are unavailable; search accepts at most 10 results per request; playlist item contents are returned only for playlists the user owns or collaborates on. Development Mode additionally requires the app owner to have Premium and limits new apps to one client ID and five users. No Spotify API request or live check was made. Sources: https://developer.spotify.com/policy (II.4, III.13), https://developer.spotify.com/documentation/web-api/tutorials/february-2026-migration-guide, and https://developer.spotify.com/documentation/web-api/concepts/quota-modes. |
Playlist | planned · not implemented · source review required | Not implemented: Spotify’s Developer Policy prohibits offering Spotify metadata, cover art, or audio previews as a standalone service/product and prohibits analyzing Spotify content/service for derived listenership metrics, benchmarking, user metrics, or user profiling. Display requires Spotify attribution/marks and a link to the matching content. SignalShelf’s paid standalone API therefore needs written Spotify permission or a separate license before implementation or API calls. Current contract limitations also differ from older examples: since the 2026 Web API changes, artist follower/popularity fields and artist top tracks are unavailable; search accepts at most 10 results per request; playlist item contents are returned only for playlists the user owns or collaborates on. Development Mode additionally requires the app owner to have Premium and limits new apps to one client ID and five users. No Spotify API request or live check was made. Sources: https://developer.spotify.com/policy (II.4, III.13), https://developer.spotify.com/documentation/web-api/tutorials/february-2026-migration-guide, and https://developer.spotify.com/documentation/web-api/concepts/quota-modes. |
Search | planned · not implemented · source review required | Not implemented: Spotify’s Developer Policy prohibits offering Spotify metadata, cover art, or audio previews as a standalone service/product and prohibits analyzing Spotify content/service for derived listenership metrics, benchmarking, user metrics, or user profiling. Display requires Spotify attribution/marks and a link to the matching content. SignalShelf’s paid standalone API therefore needs written Spotify permission or a separate license before implementation or API calls. Current contract limitations also differ from older examples: since the 2026 Web API changes, artist follower/popularity fields and artist top tracks are unavailable; search accepts at most 10 results per request; playlist item contents are returned only for playlists the user owns or collaborates on. Development Mode additionally requires the app owner to have Premium and limits new apps to one client ID and five users. No Spotify API request or live check was made. Sources: https://developer.spotify.com/policy (II.4, III.13), https://developer.spotify.com/documentation/web-api/tutorials/february-2026-migration-guide, and https://developer.spotify.com/documentation/web-api/concepts/quota-modes. |
Podcast | planned · not implemented · source review required | Not implemented: Spotify’s Developer Policy prohibits offering Spotify metadata, cover art, or audio previews as a standalone service/product and prohibits analyzing Spotify content/service for derived listenership metrics, benchmarking, user metrics, or user profiling. Display requires Spotify attribution/marks and a link to the matching content. SignalShelf’s paid standalone API therefore needs written Spotify permission or a separate license before implementation or API calls. Current contract limitations also differ from older examples: since the 2026 Web API changes, artist follower/popularity fields and artist top tracks are unavailable; search accepts at most 10 results per request; playlist item contents are returned only for playlists the user owns or collaborates on. Development Mode additionally requires the app owner to have Premium and limits new apps to one client ID and five users. No Spotify API request or live check was made. Sources: https://developer.spotify.com/policy (II.4, III.13), https://developer.spotify.com/documentation/web-api/tutorials/february-2026-migration-guide, and https://developer.spotify.com/documentation/web-api/concepts/quota-modes. |
Podcast Episodes | planned · not implemented · source review required | Not implemented: Spotify’s Developer Policy prohibits offering Spotify metadata, cover art, or audio previews as a standalone service/product and prohibits analyzing Spotify content/service for derived listenership metrics, benchmarking, user metrics, or user profiling. Display requires Spotify attribution/marks and a link to the matching content. SignalShelf’s paid standalone API therefore needs written Spotify permission or a separate license before implementation or API calls. Current contract limitations also differ from older examples: since the 2026 Web API changes, artist follower/popularity fields and artist top tracks are unavailable; search accepts at most 10 results per request; playlist item contents are returned only for playlists the user owns or collaborates on. Development Mode additionally requires the app owner to have Premium and limits new apps to one client ID and five users. No Spotify API request or live check was made. Sources: https://developer.spotify.com/policy (II.4, III.13), https://developer.spotify.com/documentation/web-api/tutorials/february-2026-migration-guide, and https://developer.spotify.com/documentation/web-api/concepts/quota-modes. |
SoundCloud
| Field | Type | Description |
|---|---|---|
Artist | planned · not implemented · source review required | Not implemented. SoundCloud allows only listed commercial uses or another use it approves case-by-case; its terms prohibit renting/selling API access or User Content/Personal Data, reselling SoundCloud services, and persistent User Content caching beyond session operation. A paid, multi-customer creator-data API is not established as permitted by those terms. Do not make API calls or scrape pages for this product unless SoundCloud gives written approval for the exact product, fields, paid customer access, redistribution, caching, retention, and deletion. Its public API spec documents user and track resource endpoints, but an endpoint existing does not grant this product use. Sources: https://developers.soundcloud.com/docs/api/terms-of-use and https://developers.soundcloud.com/docs/api/explorer/open-api. |
Artist Tracks | planned · not implemented · source review required | Not implemented. SoundCloud allows only listed commercial uses or another use it approves case-by-case; its terms prohibit renting/selling API access or User Content/Personal Data, reselling SoundCloud services, and persistent User Content caching beyond session operation. A paid, multi-customer creator-data API is not established as permitted by those terms. Do not make API calls or scrape pages for this product unless SoundCloud gives written approval for the exact product, fields, paid customer access, redistribution, caching, retention, and deletion. Its public API spec documents user and track resource endpoints, but an endpoint existing does not grant this product use. Sources: https://developers.soundcloud.com/docs/api/terms-of-use and https://developers.soundcloud.com/docs/api/explorer/open-api. |
Track | planned · not implemented · source review required | Not implemented. SoundCloud allows only listed commercial uses or another use it approves case-by-case; its terms prohibit renting/selling API access or User Content/Personal Data, reselling SoundCloud services, and persistent User Content caching beyond session operation. A paid, multi-customer creator-data API is not established as permitted by those terms. Do not make API calls or scrape pages for this product unless SoundCloud gives written approval for the exact product, fields, paid customer access, redistribution, caching, retention, and deletion. Its public API spec documents user and track resource endpoints, but an endpoint existing does not grant this product use. Sources: https://developers.soundcloud.com/docs/api/terms-of-use and https://developers.soundcloud.com/docs/api/explorer/open-api. |
Kwai
| Field | Type | Description |
|---|---|---|
Profile | implemented · local checks only · production blocked by default | GET /v1/kwai/profile (catalog path). GET /v1/kwai/profile. Partial owner-authorized mapping through Kuaishou Open Platform `GET /openapi/user_info` with the user-consented `user_info` scope. Reads only the account connected by the authenticated SignalShelf user; arbitrary handle/profile URL lookup is unavailable because the official response does not expose a verified handle for matching. Maps only returned public name, gender, avatar, city, and follower/following counts. Local provider simulation only; no Kwai credentials or live request. Developer app approval, privacy/retention review, paid-use clearance, and live validation remain required, so production stays gated. Sources: https://open.kuaishou.com/platformDocs/openAbility/userInformation/publicInformation.html and https://open.kuaishou.com/platformDocs/develop/web-app. |
User Posts | implemented · local checks only · production blocked by default | GET /v1/kwai/user/posts (catalog path). GET /v1/kwai/user/posts. Partial owner-authorized mapping through Kuaishou Open Platform `GET /openapi/photo/list` and the `user_video_info` scope. Reads only the connected account’s own video list; arbitrary handles/profile URLs are unavailable. Supports source page size up to 200 and photo-ID cursors; only documented video fields are mapped. Local provider simulation only; no Kwai credentials or live request. Developer app approval, privacy/retention review, paid-use clearance, and live validation remain required, so production stays gated. Sources: https://open.kuaishou.com/platformDocs/openAbility/contentManagement/searchForVideos.html and https://open.kuaishou.com/platformDocs/develop/web-app. |
Post | implemented · local checks only · production blocked by default | GET /v1/kwai/post (catalog path). GET /v1/kwai/post. Partial owner-authorized mapping through Kuaishou Open Platform `GET /openapi/photo/info` with the `user_video_info` scope. Accepts a canonical Kwai/Kuaishou post URL only and returns the post only when Kuaishou resolves it for the connected creator account; arbitrary public post lookup is unavailable. Local provider simulation only; no Kwai credentials or live request. Developer app approval, privacy/retention review, paid-use clearance, and live validation remain required, so production stays gated. Sources: https://open.kuaishou.com/platformDocs/openAbility/contentManagement/searchForVideos.html and https://open.kuaishou.com/platformDocs/develop/web-app. |
Kick
| Field | Type | Description |
|---|---|---|
Clip Transcript | planned · not implemented · source review required | Not implemented: the current official Kick Public API OpenAPI document lists 28 paths and contains no clip lookup or transcript endpoint. Kick’s Developer Agreement prohibits selling, licensing, monetizing, or distributing API metadata/content without prior written permission; it separately prohibits redistribution and limits ordinary cache-only storage to 24 hours without sharing. Kick’s general Terms prohibit scraping and automated access. A clip API, if later documented, would not itself grant rights to download clip media, transcribe it, store transcript text, or sell/distribute the result. Obtain written permission for the clip source, commercial transcript processing and output, media rights, caching/retention, and paid redistribution before implementation; also require a transcription-provider agreement. Sources: https://api.kick.com/swagger/doc.json, https://dev.kick.com/terms-of-service, and https://kick.com/terms-of-service. |
Clip | planned · not implemented · source review required | Not implemented: the current official Kick Public API OpenAPI document lists 28 paths and documents channels, livestreams, categories, chat, events and rewards, but no clip lookup by URL or clip ID. Kick’s Developer Agreement separately prohibits selling, licensing, monetizing, or distributing API metadata/content without prior written permission; it also prohibits redistribution, and limits ordinary cache-only storage to 24 hours without sharing. Kick’s general Terms prohibit scraping and automated access. Do not use undocumented endpoints or scrape Kick pages. Obtain a documented clip-read contract and written permission expressly covering SignalShelf’s paid customer API, fields, caching, and redistribution before implementation. Sources: https://api.kick.com/swagger/doc.json, https://dev.kick.com/terms-of-service, and https://kick.com/terms-of-service. |
Snapchat
| Field | Type | Description |
|---|---|---|
User Profile | implemented · local checks only · production blocked by default | GET /v1/snapchat/profile (catalog path). GET /v1/snapchat/profile. Uses the official Snap Public Profile API search endpoint with a Snap Business OAuth token and exact Snap username matching. Returns only documented public fields; following/post counts and private-account data are unavailable. A local integration check verifies OAuth token rotation is encrypted in PostgreSQL and reused after process-cache reset. Live access still requires Snap API allowlisting and written paid-use/retention clearance; live source behavior is not verified. Sources: https://developers.snap.com/marketing-api/Public-Profile-API/GetStarted, https://developers.snap.com/marketing-api/Public-Profile-API/CreatorDiscovery, https://developers.snap.com/marketing-api/Public-Profile-API/Profiles. |
Spotlight by Link | implemented · local checks only · production blocked by default | GET /v1/snapchat/spotlight (catalog path). GET /api/v1/snapchat/spotlight. Implemented through Snap Public Profile API username search, exact Spotlight-by-ID retrieval, and public Spotlight view/share metrics. The mapping omits comment counts, generated summaries, and media dimensions because the reviewed official API does not document those fields. A local integration check verifies encrypted OAuth refresh-token rotation persists in PostgreSQL and is reused after process-cache reset. Snap API allowlisting, written paid-use/retention clearance, and live source validation remain outstanding. Sources: https://developers.snap.com/marketing-api/Public-Profile-API/ProfileAssetManagement, https://developers.snap.com/marketing-api/Public-Profile-API/Metrics, and https://developers.snap.com/marketing-api/Public-Profile-API/GetStarted. |
Spotlight Comments by Link | planned · not implemented · source review required | Source review required before implementation: Snap requires permission for automated extraction and third-party access. See the source gate in docs/LAUNCH.md. Source: https://www.snap.com/terms. |
Telegram
| Field | Type | Description |
|---|---|---|
Channel Details | planned · not implemented · source review required | Not implemented. Telegram’s Content Licensing terms restrict platform-data access to what is strictly required to operate a legitimate Telegram client, bot, or Mini App. Bot Developer Terms prohibit collection, storage, aggregation, or processing beyond what is essential to the service and specifically prohibit scraping public group/channel contents to create large datasets. The documented MTProto messages.getHistory method is user-only; Bot API updates deliver incoming channel_post events to bots with access and do not provide arbitrary historical channel search. SignalShelf’s multi-customer public channel research API is not authorized by these mechanisms. Keep unavailable unless Telegram provides written approval explicitly covering this product and scope; do not scrape or aggregate channel histories. A separately scoped customer-owned-channel ingestion feature would need its own contract, consent, bot access, purpose limitation, retention/deletion, and product review and would not establish parity for these arbitrary-channel routes. Sources: https://telegram.org/tos/content-licensing, https://telegram.org/tos/bot-developers, https://core.telegram.org/api/terms, https://core.telegram.org/method/messages.getHistory, and https://core.telegram.org/bots/api. |
Channel Posts | planned · not implemented · source review required | Not implemented. Telegram’s Content Licensing terms restrict platform-data access to what is strictly required to operate a legitimate Telegram client, bot, or Mini App. Bot Developer Terms prohibit collection, storage, aggregation, or processing beyond what is essential to the service and specifically prohibit scraping public group/channel contents to create large datasets. The documented MTProto messages.getHistory method is user-only; Bot API updates deliver incoming channel_post events to bots with access and do not provide arbitrary historical channel search. SignalShelf’s multi-customer public channel research API is not authorized by these mechanisms. Keep unavailable unless Telegram provides written approval explicitly covering this product and scope; do not scrape or aggregate channel histories. A separately scoped customer-owned-channel ingestion feature would need its own contract, consent, bot access, purpose limitation, retention/deletion, and product review and would not establish parity for these arbitrary-channel routes. Sources: https://telegram.org/tos/content-licensing, https://telegram.org/tos/bot-developers, https://core.telegram.org/api/terms, https://core.telegram.org/method/messages.getHistory, and https://core.telegram.org/bots/api. |
Post Details | planned · not implemented · source review required | Not implemented. Telegram’s Content Licensing terms restrict platform-data access to what is strictly required to operate a legitimate Telegram client, bot, or Mini App. Bot Developer Terms prohibit collection, storage, aggregation, or processing beyond what is essential to the service and specifically prohibit scraping public group/channel contents to create large datasets. The documented MTProto messages.getHistory method is user-only; Bot API updates deliver incoming channel_post events to bots with access and do not provide arbitrary historical channel search. SignalShelf’s multi-customer public channel research API is not authorized by these mechanisms. Keep unavailable unless Telegram provides written approval explicitly covering this product and scope; do not scrape or aggregate channel histories. A separately scoped customer-owned-channel ingestion feature would need its own contract, consent, bot access, purpose limitation, retention/deletion, and product review and would not establish parity for these arbitrary-channel routes. Sources: https://telegram.org/tos/content-licensing, https://telegram.org/tos/bot-developers, https://core.telegram.org/api/terms, https://core.telegram.org/method/messages.getHistory, and https://core.telegram.org/bots/api. |
Cosmos
| Field | Type | Description |
|---|---|---|
Profile | planned · not implemented · source review required | Source review required before implementation: Cosmos Terms (last updated 2025-09-25) §8(F) prohibit using spiders, robots, crawlers, data-mining tools, or similar tools to access/search/download service content; §8(I) restrict collecting or storing other users’ personally identifiable information without express permission. No public Cosmos API matching these profile/post/collection/search routes is documented. Request written authorization, a first-party API contract, personal-data permissions, and paid redistribution/retention rights from hey@cosmos.so before implementation. Do not use unofficial/private site endpoints. Source: https://www.cosmos.so/legal/terms-conditions. |
User Posts | planned · not implemented · source review required | Source review required before implementation: Cosmos Terms (last updated 2025-09-25) §8(F) prohibit using spiders, robots, crawlers, data-mining tools, or similar tools to access/search/download service content; §8(I) restrict collecting or storing other users’ personally identifiable information without express permission. No public Cosmos API matching these profile/post/collection/search routes is documented. Request written authorization, a first-party API contract, personal-data permissions, and paid redistribution/retention rights from hey@cosmos.so before implementation. Do not use unofficial/private site endpoints. Source: https://www.cosmos.so/legal/terms-conditions. |
User Collections | planned · not implemented · source review required | Source review required before implementation: Cosmos Terms (last updated 2025-09-25) §8(F) prohibit using spiders, robots, crawlers, data-mining tools, or similar tools to access/search/download service content; §8(I) restrict collecting or storing other users’ personally identifiable information without express permission. No public Cosmos API matching these profile/post/collection/search routes is documented. Request written authorization, a first-party API contract, personal-data permissions, and paid redistribution/retention rights from hey@cosmos.so before implementation. Do not use unofficial/private site endpoints. Source: https://www.cosmos.so/legal/terms-conditions. |
Post | planned · not implemented · source review required | Source review required before implementation: Cosmos Terms (last updated 2025-09-25) §8(F) prohibit using spiders, robots, crawlers, data-mining tools, or similar tools to access/search/download service content; §8(I) restrict collecting or storing other users’ personally identifiable information without express permission. No public Cosmos API matching these profile/post/collection/search routes is documented. Request written authorization, a first-party API contract, personal-data permissions, and paid redistribution/retention rights from hey@cosmos.so before implementation. Do not use unofficial/private site endpoints. Source: https://www.cosmos.so/legal/terms-conditions. |
Collection | planned · not implemented · source review required | Source review required before implementation: Cosmos Terms (last updated 2025-09-25) §8(F) prohibit using spiders, robots, crawlers, data-mining tools, or similar tools to access/search/download service content; §8(I) restrict collecting or storing other users’ personally identifiable information without express permission. No public Cosmos API matching these profile/post/collection/search routes is documented. Request written authorization, a first-party API contract, personal-data permissions, and paid redistribution/retention rights from hey@cosmos.so before implementation. Do not use unofficial/private site endpoints. Source: https://www.cosmos.so/legal/terms-conditions. |
Collection Posts | planned · not implemented · source review required | Source review required before implementation: Cosmos Terms (last updated 2025-09-25) §8(F) prohibit using spiders, robots, crawlers, data-mining tools, or similar tools to access/search/download service content; §8(I) restrict collecting or storing other users’ personally identifiable information without express permission. No public Cosmos API matching these profile/post/collection/search routes is documented. Request written authorization, a first-party API contract, personal-data permissions, and paid redistribution/retention rights from hey@cosmos.so before implementation. Do not use unofficial/private site endpoints. Source: https://www.cosmos.so/legal/terms-conditions. |
Search | planned · not implemented · source review required | Source review required before implementation: Cosmos Terms (last updated 2025-09-25) §8(F) prohibit using spiders, robots, crawlers, data-mining tools, or similar tools to access/search/download service content; §8(I) restrict collecting or storing other users’ personally identifiable information without express permission. No public Cosmos API matching these profile/post/collection/search routes is documented. Request written authorization, a first-party API contract, personal-data permissions, and paid redistribution/retention rights from hey@cosmos.so before implementation. Do not use unofficial/private site endpoints. Source: https://www.cosmos.so/legal/terms-conditions. |
Creator Tools
| Field | Type | Description |
|---|---|---|
Find Social Profiles | planned · not implemented · source review required | Source review required before implementation: creator email discovery and age/gender inference involve personal data; confirm lawful basis, source rights, accuracy and notice requirements before building or selling these operations. |
Find Creator Emails | planned · not implemented · source review required | Source review required before implementation: creator email discovery and age/gender inference involve personal data; confirm lawful basis, source rights, accuracy and notice requirements before building or selling these operations. |
Get Age and Gender | planned · not implemented · source review required | Source review required before implementation: creator email discovery and age/gender inference involve personal data; confirm lawful basis, source rights, accuracy and notice requirements before building or selling these operations. |
Linktree
| Field | Type | Description |
|---|---|---|
Linktree page | planned · not implemented · source review required | Not implemented: Linktree Terms effective 2026-07-05 prohibit scripts, bots, scraping tools, and other automated collection from profiles or the platform. Linktree invites developers to request API/SDK access, but that page describes integrations and does not establish a public profile-read API. Linktree Developer Terms require prior use-case approval before production integration; their Marketplace terms also restrict charging end users for a Link App unless the permitted purpose or Partner Agreement expressly allows it. Request written approval and a versioned API contract specifically covering public profile lookup, SignalShelf’s paid API redistribution, fields, permissions, caching, retention, and fees before implementation. Do not fetch public profile pages or use undocumented endpoints. Sources: https://linktr.ee/s/terms, https://linktr.ee/marketplace/developer, and https://linktr.ee/about/developer-terms. |
Komi
| Field | Type | Description |
|---|---|---|
Komi page | planned · not implemented · source review required | Source review required: Komi terms prohibit scraping, scripting, automation, and copying/indexing platform content. Do not implement or offer this route without written authorization or an approved API. |
Pillar
| Field | Type | Description |
|---|---|---|
Pillar page | planned · not implemented · source review required | Source review required: Pillar terms prohibit automated searching or downloading through crawlers/data-mining tools. Do not implement or offer this route without written authorization or an approved API. |
Linkbio
| Field | Type | Description |
|---|---|---|
Linkbio page | planned · not implemented · source review required | Source review required before implementation: the documented Lnk.Bio API is OAuth 2.0 and returns /me plus the authenticated owner’s own link list; it does not establish anonymous or arbitrary third-party page lookup matching this route’s required url input. Lnk.Bio distinguishes private apps (own account only, no review) from public apps (other accounts only after they authorize the app; Lnk.Bio review required). Before any owner-authorized partial, register and obtain approval for a public app, confirm its exact read scope and OAuth/token lifecycle, and obtain written clearance for SignalShelf’s paid customer access, storage/retention, and redistribution. A connected-owner implementation would be a separately disclosed partial, not parity with arbitrary URL lookup. Sources: https://api.lnk.bio/, https://api.lnk.bio/doc-498638, https://api.lnk.bio/doc-498664, https://api.lnk.bio/api-6746006, https://api.lnk.bio/api-6746007, and https://lnk.bio/terms-and-conditions?sc=en. |
Amazon Shop
| Field | Type | Description |
|---|---|---|
Amazon Shop page | planned · not implemented · source review required | Source review required before implementation: Amazon Creators API documents product catalog search/details/variations/browse nodes, not lookup or enumeration of arbitrary influencer storefronts. Access requires Associates enrollment, qualifying sales, registration, and credentials; Associates policies restrict Program Content to permitted Associates promotional use, prohibit resale/redistribution and data-mining, and require express prior written approval for some aggregation, analysis, repurposing, or third-party app use. Standard Creators API access does not authorize SignalShelf’s paid multi-customer storefront-data API. Keep this operation unavailable unless Amazon or another licensed source provides written rights for arbitrary storefront lookup, exact fields, paid customer API delivery, caching, retention, and redistribution. Sources: https://affiliate-program.amazon.com/creatorsapi/docs/en-us/introduction, https://affiliate-program.amazon.com/creatorsapi/docs/en-us/api-reference/operations/search-items, and https://affiliate-program.amazon.com/help/operating/policies. |
Scrape Creators
| Field | Type | Description |
|---|---|---|
Get credit balance | implemented · local checks only | GET /v1/account/credit-balance (catalog path). GET /api/v1/account/credits. Authorized reference response shape sampled on 2026-11-02: success, creditCount, message; its published OpenAPI example also lists credits_remaining and credits_charged. SignalShelf returns its own authenticated balance, never Scrape Creators account data. Sanitized fields/types only; no account values retained. |
Get request history | implemented · local checks only | GET /v1/account/get-api-usage (catalog path). GET /api/v1/account/requests. Authorized reference response sampled on 2026-11-02 included sensitive field names for API tokens/keys, IP addresses, user/team IDs, and user agents. SignalShelf deliberately returns only the documented allowlist and reconstructs request_time from completion time and duration. Only field names/types/count were retained; no request values or identifiers are stored. |
Get daily usage | implemented · local checks only | GET /v1/account/get-daily-usage-count (catalog path). GET /api/v1/account/daily-usage. Authorized reference response sampled on 2026-11-02 returned usage_date and string-valued total_credits/request_count. SignalShelf uses these field names/types for its own authenticated account’s prior 30-day UTC usage; values are not Scrape Creators account data. |
Get most used routes | implemented · local checks only | GET /v1/account/get-most-used-routes (catalog path). GET /api/v1/account/top-endpoints. Authorized reference response sampled on 2026-11-02 was an empty array, so item fields could not be live-compared. SignalShelf uses the published base_endpoint/call_count/total_credits shape for its own account-scoped route totals; values are not Scrape Creators account data. |
Get credit balance | implemented · local checks only | GET /v1/credit-balance (catalog path). GET /api/v1/account/credits. Matches the documented creditCount field and returns only this authenticated SignalShelf account’s balance. It does not expose Scrape Creators billing data. Requires a SignalShelf session or API key; it is account-scoped and costs zero credits. |
Linkme
| Field | Type | Description |
|---|---|---|
Profile | planned · not implemented · source review required | Source review required: Linkme terms prohibit automated cataloging/data mining and restrict resale without written consent. Do not implement or offer this route without written authorization or an approved API. |
Explore the API in your workspace. Sample results and accepted cache hits cost zero credits. Open the playground →