You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing out service accounts, I kept getting Unauthorized, invalid project secret. See docs for more information: https://developer.mixpanel.com/reference/authentication#project-secret raised from the SDK
I ended up tracing this to the SDK never sending the project_id GET paramter to the import. This paramter is marked as required in the documentation.
...with credentials and with/without a project_id confirms the problem.
The text was updated successfully, but these errors were encountered:
beheh
changed the title
Missing project_id parameter for import endpoint
import_data does not work with Service Accounts due to missing project_id
Jul 8, 2022
beheh
changed the title
import_data does not work with Service Accounts due to missing project_idimport_data does not work with Service Accounts due to missing project_idJul 8, 2022
In fact: service accounts seem unsupported entirely by this SDK. For example, it does not appear possible to supply a api_secret=<service_account>:<secret> to this SDK, due to the project_id omission and the fact that an additional colon is appended to that string as part of the HTTP Basic auth assembly.
@beheh that is correct, this SDK does not currently support Service Accounts. You can use Service Accounts to import data with our Python utilities library, though: https://github.com/mixpanel/mixpanel-utils
While testing out service accounts, I kept getting
Unauthorized, invalid project secret. See docs for more information: https://developer.mixpanel.com/reference/authentication#project-secret
raised from the SDKI ended up tracing this to the SDK never sending the
project_id
GET paramter to theimport
. This paramter is marked as required in the documentation.Trying the following curl command:
vs.
...with credentials and with/without a project_id confirms the problem.
The text was updated successfully, but these errors were encountered: