Open items - FanFeed Partner API

Item	Owner	Status
Test credentials	FanFeed	Keys are issued per environment on request; ask and we will get you a sandbox and a production key. Confirm which environment a key resolved to with `GET /v1/health`.
On-device ingest: proxy vs. scoped token	Both	Settled 2026-08-27: proxy. Device → your backend → FanFeed; your backend holds the key. Scoped per-user tokens are not planned and no issuance endpoint exists. See Authentication.
Rate limits	FanFeed	Implemented and currently disabled. Three independent budgets, `429` with `Retry-After`, and can be enabled per key without a deploy or a contract change. See Authentication.
Load testing against your expected volume	Both	Harness built and ready to run; waiting on your traffic estimates. Provisional starting points, to be confirmed by that run: 120 ingest / 300 read / 60 write per minute.
Image hosting	Both	Not in scope. Photos render from the device camera roll by the id you submitted, which works in-app and breaks for anything cross-device or shareable. If your mock-ups need either, raise it; it is a new endpoint and it is not currently planned.
Account deletion	Both	Not an endpoint. If your app creates accounts, App Store review requires an in-app deletion path. Route those requests to us during the integration and we will delete the profile. If your volume needs an API for it, that is a contract addition; raise it early.
Your UI designs	Partner	Share them and we will confirm nothing is missing from these five endpoints

This document is updated whenever something meaningful changes; the hosted version is always current. If something here does not match what you need to build, raise it with us.