The old project names in the API stop working on December 1, 2026 at 09:00 UTC. Until then old and new names both work, so you can switch today. If you only use the dashboard, there is nothing to do.
Projects are now products
What the rename changes in the dashboard, what to update in your API calls, and by when.
Projects are now called products. A product is a tag for something you sell: an app, a site or a brand. Your existing projects became products on their own, with the same ids, the same accounts and the same app connections.
What changed in the dashboard
- Products live in Tags. The Projects page is gone. To create a product, click New Tag and turn on Product. The switch is set once, when the tag is created.
- Integrations suggest products. When you connect RevenueCat or Superwall, each app shows a matching product, or offers to create one, so you finish the setup in one place.
- "Visible to creators" moved. You now set it only where it matters: in a campaign's payout conditions. The tag sheet no longer shows it.
Filters, saved links and campaign conditions that used a project keep working.
What changes in the API
Until December 1, 2026 old and new names both work. From then on the old routes and the projects filter are refused, and responses carry the new names only.
The last row is the only one without a deadline: requests may keep the old values. The new values are the documented ones, so switch them when you touch the code anyway.
Three details to get right:
tagsmatches all listed tags. The oldprojectsfilter matched any of them. If you passed several ids, sendtagGroups=any:<id>,<id>instead.- Responses switch on the date, not before. Until December 1 a product's tag still comes back as
scope: "project", and lists carry bothprojectsandproducts. Readproductsnow, and accept both scope values. - Ids stay. Ids that start with
orgproj_remain valid for good. New products get ids that start withorgprod_. If your code checks the prefix, accept both.
The projects filter and the account assignment endpoints were deprecated on July 2, 2026. Projects to tags has the details and the tag endpoints.
How the API tells you
While an old name still works, the response carries a Migration-Guidance header that says what to send instead. Old routes also send Deprecation and Sunset headers.
After December 1, an old route answers 410 and an old parameter answers 400. Both carry a migration object:
{
"defined": false,
"code": "GONE",
"status": 410,
"message": "GET /projects was removed. Call GET /api/v1/products instead. The request and the response are the same.",
"data": {
"migration": {
"deprecated": "GET /projects",
"guidance": "Call GET /api/v1/products instead. The request and the response are the same.",
"docsUrl": "https://viral.app/docs/brands/migrations/projects-to-products",
"removedAt": "2026-12-01T09:00:00.000Z"
}
}
}
The API reference marks every old route and parameter as deprecated, with its replacement.
Let your agent do it
Paste this into a coding agent (Claude Code, Codex, Cursor) in the repository that calls the viral.app API. It lists what it found and waits for your approval before it edits anything.
Migrate this codebase's viral.app API integration from "projects" to "products". On December 1, 2026 at 09:00 UTC the old routes and the `projects` parameter stop working, and responses switch to the new names. Until then old and new names both work, so every change below is safe to ship now.
Reference
- Guide: https://viral.app/docs/brands/migrations/projects-to-products
- OpenAPI document: https://viral.app/api/v1/openapi.json. Old operations and parameters are marked `deprecated` and carry `x-deprecation` with their replacement.
Steps
1. Find every call to the viral.app API (base URL https://viral.app/api/v1, header x-api-key) and every place that reads its responses. Search for: /projects, projects=, "projects", expand, scope, "project", none:project, orgproj_.
2. Show me a table of what you found: file and line, what the code does today, and the change from the mapping below. Stop there and wait for my approval.
3. After I approve, apply the changes. Edit only code that talks to the viral.app API.
4. Verify. Run this repository's tests and type checks. If an API key is configured, repeat one changed read request and confirm that the response has no `Migration-Guidance` header. Never print the key.
Mapping
- GET and POST /projects, PUT and DELETE /projects/{id}: use the same method on /products and /products/{id}. Request and response are unchanged.
- Query or body parameter `projects` (analytics, accounts, videos, exports): send `tags` with the same ids. `tags` matches rows that carry ALL listed tags. If the old call passed several ids and meant "any of them", send `tagGroups=any:<id>,<id>` instead.
- POST /projects/{id}/accounts/{accountId} and POST /projects/{id}/accounts/bulk: call POST /accounts/tracked/tags/bulk with { "orgAccountIds": [...], "tags": [{ "scope": "product", "tagId": "<product id>" }] }.
- DELETE /projects/{id}/accounts/{accountId} and DELETE /projects/{id}/accounts/bulk: for each account, read its tags with GET /tags/account-rules, then call PUT /accounts/tracked/{orgAccountId}/tags with that list minus the product.
- Tag objects read from a response: accept both scope "project" and scope "product". Responses switch to "product" on the date. This one breaks code that compares against "project" only.
- Response key `projects` in video and account lists: read `products`. The old key is gone on the date.
- Tag objects, the filter value none:project and expand[]=projects in a request: send scope "product", none:product and expand[]=products. The old request values stay accepted, so this is a rename without a deadline.
- Product ids: keep stored ids as they are. An id starts with orgproj_ (created before the rename) or orgprod_ (created after). Remove any check that accepts only orgproj_.
Rules
- Change only what the API requires. Do not rename my own variables, database columns or UI text unless I ask.
- This migration needs no write call to viral.app. Do not create, change or delete data there.
- If a call does not fit the mapping, list it under "needs a decision". Do not guess.
Finish with a short summary: files changed, calls migrated, and anything left for me.
Need help?
Owners and admins of workspaces that still call old names get an email with their own calls and the replacement for each. If something does not fit the table above, contact support and we will walk through it with you.