Replies: 2 comments 4 replies
-
Hey, thanks for opening a discussion. Well if the token was correct it would work, I expect. Using client ID's and tokens at the same time isn't really an issue. Did you try replacing the token with a new one? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Do you have an account with ID 1? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am running into the error mentioned above when I try to import via POST. Using the Importer's UI works just fine. I am running everything in docker containers.
Here's some log messages:
curl output when trying to submit a csv and a json file to import:
at the same time my docker containers produce the following messages:
The access token is correct. If I replace it with something obviously wrong or leave it out, the import already fails when trying to access /api/v1/about. Using the correct token I get past this point and it fails when trying to access the account information.
Could the reason be that I use a client Id for the front end but a personal access token for the POST request? Is there a way to use a clientId with a POST request?
Beta Was this translation helpful? Give feedback.
All reactions