`docs/tesla-support-form-submission.md`

58 lines
# Barrel 2 — Tesla dashboard Support Inquiry form (live-session runbook)

**Status:** PREPPED 2026-08-02 (Steve approved "both barrels" by email, TK-10138).
Barrel 1 (email to fleetapisupport@tesla.com) already SENT 2026-08-02 9:48 AM PT
(Gmail sent id 19fc3604afc7b59f, from steve@designerwallcoverings.com).
This form is the channel Tesla actually staffs — do this in a live session.

## Why live-session
Requires Tesla SSO login as **steveabramsdesigns@gmail.com** + 2FA in a real
browser. Cannot be driven headless from email.

## Steps (~5 min)
1. Real browser → https://developer.tesla.com/dashboard — sign in
   (steveabramsdesigns@gmail.com, complete 2FA).
2. Open the app **"Steven Abrams" (app 72246)** (or either app — both share the
   broken record).
3. Find the **Support Inquiry** link (dashboard footer/help area — Tesla's
   official replacement for the retired email support).
4. Category: **Fleet API** (or closest: API / OAuth / Technical issue).
5. Paste the subject + description below, verbatim. Plain text only — no
   markdown tables render in the form; the description below is already
   flattened.
6. Submit, screenshot the confirmation / case number, and note it back into
   this file + TK-10138.

## Subject (paste)
Fleet API: consent fails with "No policy rules" — apps bound to foreign default_api_id 8513

## Description (paste, plain text)
Account: steveabramsdesigns@gmail.com
Product: Charge & Explore (chargeandexplore.com) — third-party Fleet API app (read-only scopes: openid, offline_access, vehicle_device_data, vehicle_location)

PROBLEM
User OAuth (/oauth2/v3/authorize) fails at the consent step with: "Something went wrong. Try again later" — "No policy rules". Reproduced repeatedly in a real browser.
Reference IDs:
- 7b149f64-c52c-42c4-b34d-7b558cb726cb
- caf17ec0-258f-4eba-b6bc-8105b2c75b27

ROOT CAUSE (from GET /oauth2/v3/clientinfo)
Both of our apps have default_api_id = 8513, but API record 8513 is owned by a different developer's app and has no consent policy:
- App "Steven Abrams", app.id 72246, client_id 9e4d27da-c154-4630-85fe-1b216f8901b0, default_api_id 8513
- App "8226", app.id 72462, client_id 370f23c4-4fba-403b-b11c-c42e6a09902e, default_api_id 8513
Record 8513: owner_app_id 71851 ("Millie Vehicle Assistant" — NOT ours); policy_id null (this is the "No policy rules" failure); identifier is the space-joined NA+EU audience string.

Partner registration is complete (GET partner_accounts/public_key verifies on NA; our public key matches). The dashboard does not expose a way to change region/audience, so we cannot obtain a unique, self-owned API record.

REQUEST
1. Assign our apps (72246 and/or 72462) their OWN API audience record with a valid consent policy, not the foreign shared record 8513; or
2. Enable us to select a single region (North America only) so our app gets a dedicated NA audience record with its own policy.

Our redirect URIs / origins are already correctly configured (e.g. https://chargeandexplore.com/auth/tesla/callback).

Note: we also emailed this report to fleetapisupport@tesla.com on Aug 2, 2026 (same subject) — please link the two if that ticket landed.

Thank you,
Steve Abrams
steve@designerwallcoverings.com