We had a talk about this alread here.
It did work for the past year and stopped working again some weeks ago. I cannot find a way anymore to create an API-Token for a Base shared with me.
Can I get any adwise here. That would be really great.
Please consult the API reference. You’ll find all you need to know about authentication and the various tokens there.
Hi rdb,
thank you for responding so quickly. Can we dive still a little bit deeper?
It really did work until some weeks ago (more precisely, it was June, when I saw it working the last time). You can concolude from that, that I DID consult the API reference and were able to construct a working sequence of API calls. Also, the calls still work for my on base - they just stopped working for the base that was shared with me. What I use is:
- https://cloud.seatable.io/api2/auth-token/ [that works fine all the time]
- https://cloud.seatable.io/api/v2.1/workspace/{{workspaceId}}/dtable/{{baseName}}/temp-api-token/ [this also works fine]
when I use this temp-token then to try either “metadata” or “rows” I get “You don’t have permission to access.” However, I can still access this shared base in the web-view.
Does this make any sense?
You’re missing one important step. The temp-token is a so called API-Token, not a Base-Token.
You have to use also this Get Base-Token with API-Token.
Then with the returned Base-Token, you can execute API calls on the base…
Oh yes. Thanks. It’s working. 
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
