Hello!
Since I’ve worked with the REST API extensively in the past days to add coda support to powersave.pro I thought it might be useful to share feedback when it’s still on top of my mind. Overall the API was easy to use for me, the docs are clear, there’s only few limitations which prevented me from integrating Coda entirely to my app - some features so far have to be turned off.
Search
The query API parameter requires exact match. It might be good for some usecases, but for my integration I’d need a more flexible search. My extension allows to add rows to coda and I could also support right away linking the new record to other records, but I would need to let the user search for that record.
Having the ability to search would also allow me to enable the “record matching” feature where I let users edit records that match criteria for the currently visited website (editing contact record while visiting a social media profile for example)
Select options in the column API
I’m fetching the table columns from the API to auto generate a form for the coda table. If the select options came in the column response then I could render a select UI. Now this field is skipped.
Creating tables
If there was an option to create tables via API I could allow to create tables right away based on the currently visited website. It makes the flow a bit nicer to be able to save something ASAP even when the table does not exist yet.
OAuth
I could offer to “Login with Coda” and the user would not have to search for a API token in the settings. A bit more smooth onboarding.
That’s all! I understand some of these limitations might be by design.