Mixpanel import API 400 invalid project token: usage events for at-ri

Not specified by the original author.

TL;DR

Walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Start in the Mixpanel project settings, the import API response log, and the Lexicon, work on one affected item, and prove the fix there before running the full set. The named signal in this one is API 400. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Mixpanel import API 400 invalid project token - usage events for at-risk accounts rejected at ingest

Use this when

• You see this exact message or symptom in Mixpanel: Mixpanel import API 400 invalid project token - usage events for at-risk accounts rejected at ingest
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Mixpanel fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Mixpanel project settings, the import API response log, and the Lexicon and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the import payload, the project credential used by the job, the distinct_id values, and the JQL or cohort definition, and check the hand off where the test record stopped, the condition or field it failed, and the log line added there. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Verify: the corrected value or setting is visible in Mixpanel itself, not only in a local config file
4. Re-run the original operation on the single affected item first: re-import a one day slice through the import API, then re-run the scoring query on that slice only. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the event volume for at-risk accounts in Explore and the updated risk list after scoring. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Mixpanel import API 400 invalid project token - usage events for at-risk accounts rejected at ingest

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Mixpanel API 400 during the run

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does mixpanel import API 400 invalid project token - usage events for at-risk accounts rejected at ingest keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Mixpanel import API and JQL, service account authentication, current Mixpanel project settings. The steps assume you can read the job or build log and change the named object in Mixpanel.

Why it happens

In Mixpanel, this failure usually means one step in the chain checks a condition or a field that the earlier steps no longer produce, so the chain stops silently at that check. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstMBb0ER2iFRCiYt3wODKvw

Resolved from the public thread: https://vectle.com/posts/pstMBb0ER2iFRCiYt3wODKvw

Thread query: Mixpanel import API 400 invalid project token - usage events for at-risk accounts rejected at ingest

TL;DR: Walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Start in the Mixpanel project settings, the import API response log, and the Lexicon, work on one affected item, and prove the fix there before running the full set. The named signal in this one is API 400. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

Fix Mixpanel init failing with token missing

TL;DR

Mixpanel init fails when the project token is missing at init time, usually an env var that did not reach the client. Verify the token value is present before calling init, fix the env pipeline, and confirm events flow. The SDK is fine; it was started with nothing.

The error

Mixpanel init failed
Error: Token missing. mixpanel.init requires a valid project token.

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=mixpanel init failed token missing"

Fix it

Step 1: Log the token value before init

Print the token variable right before the mixpanel.init call and reload.

Expected: You see undefined or empty, confirming the value never arrived.

Step 2: Check the env var pipeline

Verify the variable is set in your build environment and prefixed correctly for client exposure.

Expected: You find the break: unset var, wrong prefix, or a build cache with the old value.

Step 3: Fix and rebuild

Set the variable correctly and trigger a fresh build.

Expected: The log shows the real token before init.

Step 4: Confirm events reach Mixpanel

Trigger an event and check the Mixpanel Live View.

Expected: Events appear within seconds.

Step 5: Guard init on the value

Skip or defer init when the token is missing, and log loudly so it never fails silently again.

Expected: A missing token becomes a visible warning, not a silent outage.

When this applies

• Mixpanel init fails with a missing token
• Events flow in one environment but not another
• You just changed build or deploy pipelines

When it doesn't

• Init succeeds but events never arrive (check the token value and project)
• The token is present and correct (check network blocking)
• You use the EU data residency endpoint (check the API host config)

Compatibility

Mixpanel JavaScript SDK. Any framework.

Variant phrasings

mixpanel token undefined init

Same failure. The env pipeline is the first place to look.

mixpanel project token missing error

A missing token at init is always a config delivery problem, never an SDK bug.

mixpanel not tracking token empty

Empty-string tokens fail the same way. Check for whitespace-only values too.

Why it happens

Client SDKs read the project token from your build-time or runtime config. When the env var is missing, mis-prefixed, or cached from an old build, init receives nothing and refuses to start. The failure is in config delivery, not in Mixpanel.

Edge cases

• Different Mixpanel projects per environment need different tokens; check you did not cross them
• Some frameworks strip env vars at build time; runtime config needs a different mechanism
• A token with trailing whitespace fails validation; trim values on load

If it still fails

• Confirm the failure in a second browser or device to rule out local blockers.
• Check the vendor status page and your CSP and adblocker setup in parallel.
• Capture console errors and the failing network responses for the vendor ticket.
• Test with a minimal page containing only the snippet to isolate framework interference.
• If the tracking is business-critical, add a server-side event path as backup.

Prevention

• Pin snippet versions and test upgrades in staging first.
• Run CSP in report mode before enforcing, so new vendors surface early.
• Monitor event volume per source; sudden drops are the early warning.
• Keep a server-side backup path for business-critical events.
• Document which env vars each snippet needs so deploys never miss one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_NBbOOvlT6npjCRK8oJbpqg

Resolved from the public thread: https://vectle.com/posts/pst_NBbOOvlT6npjCRK8oJbpqg

Thread query: mixpanel init failed token missing

TL;DR: Mixpanel init fails when the project token is missing at init time, usually an env var that did not reach the client. Verify the token value is present before calling init, fix the env pipeline, and confirm events flow. The SDK is fine; it was started with nothing.

Not specified by the original author.

Fix Amplitude SDK returning 400 on invalid API key

TL;DR

A 400 invalid API key from Amplitude means the key is wrong, revoked, or belongs to a different project. Copy the current API key from the Amplitude project settings and replace the stored value. Keys do not fix themselves; replace, do not retry.

The error

Amplitude SDK error
HTTP 400: Invalid API key

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=amplitude sdk 400 invalid api key error"

Fix it

Step 1: Copy the current API key from Amplitude

Amplitude -> Project Settings -> copy the API key for the right project.

Expected: You have the current key value.

Step 2: Compare with what your app sends

Check the stored key in your config or secrets store against the copied value.

Expected: You find the mismatch: stale key, wrong project, or a paste error.

Step 3: Replace the stored key

Update the config with the correct key and redeploy or reload.

Expected: The app now sends the current key.

Step 4: Trigger a test event

Fire an event and watch for the 400.

Expected: Events return 200 and appear in Amplitude.

Step 5: Check for other stale copies

Search CI configs, feature flags, and docs for the old key.

Expected: No stale copies remain.

When this applies

• Amplitude SDK calls fail with 400 invalid API key
• Events stopped after a key rotation or project change
• You are setting up Amplitude for the first time

When it doesn't

• The key is valid but events are malformed (check the event schema)
• The error is 401 or 403 (check the key type and permissions)
• Events work in one project but not another (check the project mapping)

Compatibility

Amplitude SDKs (HTTP API, JavaScript, and others).

Variant phrasings

amplitude invalid api key 400

Same failure. The key in Amplitude settings is the source of truth.

amplitude 400 bad request api key

The 400 wrapper usually carries the invalid-key detail. Read the response body.

amplitude key revoked events failing

Revoked keys fail exactly like wrong keys. Replace from project settings.

Why it happens

The API key identifies the Amplitude project. When it is wrong, stale, or revoked, Amplitude rejects the payload at the gate with 400. Retrying the same key never helps because the key itself is the problem.

Edge cases

• API keys differ per project; dev keys sent to prod projects fail
• Keys pasted with trailing whitespace fail; trim on load
• EU-residency projects need the EU endpoint too; the right key on the wrong endpoint still fails

If it still fails

• Confirm the failure in a second browser or device to rule out local blockers.
• Check the vendor status page and your CSP and adblocker setup in parallel.
• Capture console errors and the failing network responses for the vendor ticket.
• Test with a minimal page containing only the snippet to isolate framework interference.
• If the tracking is business-critical, add a server-side event path as backup.

Prevention

• Pin snippet versions and test upgrades in staging first.
• Run CSP in report mode before enforcing, so new vendors surface early.
• Monitor event volume per source; sudden drops are the early warning.
• Keep a server-side backup path for business-critical events.
• Document which env vars each snippet needs so deploys never miss one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CKBgITxWeEbEWfVIedwVHQ

Resolved from the public thread: https://vectle.com/posts/pst_CKBgITxWeEbEWfVIedwVHQ

Thread query: amplitude sdk 400 invalid api key error

TL;DR: A 400 invalid API key from Amplitude means the key is wrong, revoked, or belongs to a different project. Copy the current API key from the Amplitude project settings and replace the stored value. Keys do not fix themselves; replace, do not retry.