List Rows, no success yet

[nbrege]

I am still having no success getting the API to work. I can’t even get the “Try It” feature to work.
This is what I am doing:

I start with the “Get base token with API token” endpoint. I enter my API token into the Bearer field & click the Try It button. I get the following response:

{
  "app_name": "TestApp",
  "access_token": "*** token removed ***",
  "dtable_uuid": "*** uuid removed ***",
  "dtable_server": "https://cloud.seatable.io/dtable-server/",
  "dtable_socket": "https://cloud.seatable.io/",
  "dtable_db": "https://cloud.seatable.io/dtable-db/",
  "workspace_id": 49646,
  "dtable_name": "Test1",
  "use_api_gateway": true
}

I then go to the “List Rows” endpoint. Again I enter my API token in the Bearer field. I enter the dtable_uuid token from above into the base_uuid field & my table name into the table_name field. These are the only 2 required fields. When I click the Try It button I get a response of “invalid token”, as below:

{
  "error_message": "invalid token"
}

I am beyond frustrated that I can’t get this to work. Can anybody please help me? Thank you…

[daniel.pan]

@nbrege

Again I enter my API token in the Bearer field

You should use the returned “access_token” to list-rows. The API token is a permanent token to get the temporary access_token. Then you use the access_token to manipulate data in the base.

[nbrege]

Thank you, that was the key. I wish the documentation was a little clearer on that.
Also, using 2 different terms for the same thing is confusing.

[daniel.pan]

@nbrege

Also, using 2 different terms for the same thing is confusing.

It is a little confusing.

But this one-permanent token and one-temporary token way is also a common practice. I think S3 storage API also use this schema.