Overview

Forvibe Public API v1 — REST endpoints for projects, ASO, store listings, reviews, screenshots, and review simulations.

Updated 2026-05-24
4 min read

The Forvibe Public API v1 is a REST surface over the same primitives as the Forvibe MCP server. If you've used the MCP tools, every operation has a one-to-one REST counterpart. If you're building a backend integration, a mobile app, a CLI, or a webhook consumer that doesn't speak MCP, this is the API you want.

Base URL: https://forvibe.app/api/v1. Authentication: Authorization: Bearer fvk_live_… — the same personal API keys you use for MCP.

What you can do

  • Projects — list, get, create, update Forvibe projects.
  • ASO — track keywords and competitors, query App Store / Play Store search, charts and metadata.
  • Store listings — read and patch per-locale metadata; AI-translate into 175+ languages (async).
  • Reviews — pull user reviews with rating / territory / unreplied filters; aggregate stats.
  • Screenshots — list and delete project screenshots, browse Studio templates, manage Studio sessions.
  • Review simulations — trigger Forvibe's App Store rejection predictor on your metadata (async).

REST vs MCP — when to use which

Use MCP when you want an AI assistant (Claude, Cursor, Codex, ChatGPT, Gemini) to act on your Forvibe data inside a chat. Use the Public API v1 when you're writing code — a backend that auto-publishes listings, a CI step that runs review simulations, a mobile app that surfaces reviews, a chatbot that answers user feedback.

Both share the same API keys, scopes, rate limits, and credit accounting. A single fvk_live_* key works for both transports — no separate provisioning.

Conventions

  • JSON over HTTPS. Content-Type: application/json on requests, returned on responses.
  • Bearer token in the Authorization header. No cookies, no session state.
  • All field names are snake_case (matches our MCP tool outputs).
  • Errors return { error: { code, message, details?, request_id } } with a meaningful HTTP status.
  • Every response includes X-API-Version, X-Request-Id, and rate-limit headers.
  • Long-running work (AI translations, review simulations) returns 202 Accepted + a job_id to poll.

OpenAPI 3.1

Machine-readable spec at `/api/v1/openapi.json`. Import into Postman, generate SDKs with openapi-typescript-codegen, or browse it in Stoplight Studio.

Need MCP-style usage instead? See the MCP Server section.