Hi Vercel team,
I'm the developer/owner of the Webture Marketplace integration, and I'm running into an issue during the Vercel installation flow.
The OAuth flow reaches Vercel's "Completing Installation..." page successfully, but the installation never actually completes.
On the completion page:
https://vercel.com/webture/~/integrations/icfg_mL4L6ovFwM34452WqXDy8NsT/installed
Vercel's own frontend makes these requests:
POST /api/v1/integrations/configuration/icfg_mL4L6ovFwM34452WqXDy8NsT/complete?teamId=webture
→ 404
and:
GET /api/v1/integrations/configuration/icfg_mL4L6ovFwM34452WqXDy8NsT?teamId=webture
→ 404
The important part is that these are requests made by Vercel's installation/completion page to Vercel's own API. They fail before the installation is finalized.
The team slug being passed is: webture
The resolved Vercel team ID for this team is: team_cvZcLxuQVBWW1rIFwyKWS9Qy
We have confirmed that this team ID is valid and corresponds to our team through our server-side OAuth exchange logs for the same installation.
Because the completion requests return 404, the installation never gets finalized. This subsequently causes the access token generated by the flow to be rejected with "invalidToken" when our integration tries to use it, including when accessing the configuration itself.
This makes us believe the token error is a consequence of the installation not being finalized, rather than an OAuth scope/token problem.
Could someone from the Vercel Marketplace/Integrations engineering team please check the state of this configuration/installation on Vercel's side and determine why these configuration endpoints are returning 404?
I'm happy to provide:
- request IDs
- timestamps
- browser network logs
- server-side OAuth exchange logs
- screenshots/video of the installation flow
I have intentionally not included any access tokens or client secrets here.