Improvement
Runnable creator discovery examples
The cookbook now includes a complete Next.js creator search app, campaign comparison, and CSV export. The shortlist, lookalike and existing-list scoring recipes include complete bounded CLI workflows, expected output, costs and recovery guidance.The creator research app adds evidence review and saved API shortlists with no dependency installation. Download its v1.1.0 source archive.Fork the MIT example code from Influship examples or download the reviewed v1.0.0 source archives. Each recipe links its source, the TypeScript SDK guide, relevant API contracts and related workflows.Improvement
Durable media URLs from GET /v1/posts
GET /v1/posts now returns durable hosted image URLs for media.url, media.thumbnail_url, and carousel_items[].thumbnail_url whenever a hosted copy is available. Previously these were platform links that expire within days. When no hosted copy exists, you still get the platform URL, which expires, so download it promptly. The response shape is unchanged.Live and raw endpoints under /v1/raw/ are unchanged: they return fresh platform URLs on each request.Fix
Live-data errors and ingest quota updates
Live and raw Instagram, YouTube, and TikTok endpoints now return503 service_unavailable in the standard error envelope whenever live data is temporarily unavailable. Previously some of these cases surfaced as a generic 500 internal_error or a non-standard body. Retry 503 responses with bounded backoff, honoring Retry-After when present; you are not charged for them. See Error Handling.POST /v1/creators/ingest no longer consumes your daily ingest quota when the handle does not exist (404) or cannot be validated right now (503). A slot is only used once the request is accepted. See Ingest Creators On Demand.Improvement
Breaking raw Instagram profile contract update
GET /v1/raw/instagram/profile/{username} no longer returns highlight_reel_count, is_business, or is_professional. Remove reads of these properties from your integration.media_count is required but nullable. Handle null as an unavailable lifetime total; 0 means an observed empty profile. Do not substitute the number of returned posts for the lifetime total. Cached Instagram profiles and TikTok responses are unchanged.This changes the existing /v1 response contract. Update response validators and null handling before consuming the new response. See SDK guidance for client examples.Feature
YouTube discovery, pagination, and video details
YouTube search now supports upload-date, popularity, content-type, duration, country, and language filters. Responses include an opaquenext_cursor; pass it back as cursor to fetch another page. Search costs 0.5 credits per fetched page, independent of the number of results returned.Two new endpoints expand topic discovery and validation:GET /v1/raw/youtube/typeaheadreturns localized query suggestionsGET /v1/raw/youtube/video/{video_id}returns fresh views, likes, comments, duration, tags, and exact publication data when available
Fix
Search evidence fields in TypeScript
Generated TypeScript types now include the documentedconfidence, low_confidence, and structured evidence fields on search matches. Structured evidence stays in the same order as the plain-text reasons list.Fix
Automatic recovery for raw Instagram requests
Raw Instagram profile, post, and transcript requests now recover automatically from temporary source-platform interruptions. Confirmed missing posts, missing profiles, and private profiles continue to return their documented errors.Batch post and transcript requests now stop when your request expires or disconnects. Batch results remain in the same order as the requested shortcodes.Fix
Raw Instagram post & transcript reliability
Fixed errors affecting Instagram post lookups and video transcripts after a source-platform change. Individual post lookup, batch post lookup, and transcript endpoints now return consistent response shapes across the REST API, MCP tools, and no-code actors.Temporary source-platform failures now return retryable429/503 responses with Retry-After instead of a generic 500. Use the same backoff as other live-data requests — see Error Handling.Affected endpoints:GET /v1/raw/instagram/post/{shortcode}POST /v1/raw/instagram/postsGET /v1/raw/instagram/transcript/{shortcode}POST /v1/raw/instagram/transcripts
Feature
Raw Instagram post lookup and transcripts
You can now look up an individual Instagram post by shortcode and fetch video transcripts directly from the raw API. These endpoints return fresh raw post data, including fields that are not guaranteed on cached post-list responses, such as coauthors, paid partnership flags, tagged users, product mentions, display resources, video versions, music attribution, and location data.Available endpoints:GET /v1/raw/instagram/post/{shortcode}for one postPOST /v1/raw/instagram/postsfor up to 20 posts in one requestGET /v1/raw/instagram/transcript/{shortcode}for one video post transcriptPOST /v1/raw/instagram/transcriptsfor up to 10 video post transcripts in one request
post; call the post lookup endpoint separately when you need post metadata alongside a cached transcript.We’ve also added two Apify actors for no-code and workflow use cases:- Instagram Post Lookup
- Instagram Post Transcripts
Feature
MCP Server
The Influship MCP server launched atmcp.influship.com/mcp with eight typed tools. Connect any Model Context Protocol-compatible client, including Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT Connectors, and VS Code. The MCP Server guide lists the current tools for each endpoint.Feature
Pay per request with x402 (no API key needed)
Anonymous AI agents can now call supported paid Influship endpoints via the x402 payment protocol. The agent makes a request without anX-API-Key, gets a 402 Payment Required response with a USDC-on-Base price, signs a payment, and retries without signup or billing setup.Feature
Pay with MPP (Stripe cards or USDC on Tempo)
The Machine Payments Protocol — Stripe and Tempo’s open standard for HTTP-native machine-to-machine payments — coexists with x402 on the same endpoints. Pay per request via Stripe SPT (Shared Payment Tokens, USD via card) or USDC on Tempo. Pick whichever rail your client supports; the API accepts both.Feature
Weighted lookalike seeds
Lookalike search now accepts up to 10 seeds with individual weights (0-1). Higher weights make the API lean more heavily on that seed’s characteristics when ranking results.This is particularly useful when you have campaign performance data — weight your best performers higher and the API finds more creators who skew toward that profile.Improvement
Search fees and usage headers
Search billing separates the base fee from the per-creator delivery fee. Response headers report credit usage and remaining rate-limit budgets.Feature
Campaign match endpoint
POST /v1/creators/match scores creators against a campaign brief. Each result includes a decision (good, neutral, or avoid), a numeric score, and human-readable reasoning.The intent.query field (500 chars) describes the campaign. The optional intent.context field (2,000 chars) adds background — target demographics, content format preferences, brand guidelines.See Match Reasons for how to interpret the output.Improvement
Credit-based rate limiting with trust tiers
Rate limits are now enforced using credit budgets instead of simple request counts. Heavier endpoints consume more budget than lighter ones. Trust tiers increase your limits based on lifetime spend — and never downgrade.See Rate Limits & Tiers for the full tier table.Feature
Feature