This message was deleted.

@witty-vegetable-47981 I believe that Rearc is using an isolated instance, so you'd want to replace the URL https://api.secoda.co/ with your isolated instance's URL. If that's not the case let me know and I can investigate further

@elegant-house-93198 Thanks. If I hit

https://<custom>.<http://secoda.co|secoda.co>

for the web console, is the api at

/api

under that? Or

<custom>-<http://api.secoda.co|api.secoda.co>

? Or is there somewhere I can look up what the api prefix should be for us?

@wonderful-army-60594 do you know the answer to David's question, I'm fairly certain it should be

https://<custom>.secoda/co/api/v1

but I'll let Carter confirm

Hi David. Your python code is syntactically correct. However, since Rearc is on a managed instance, you will have to hit the endpoint https://rearc.secoda.co/api/v1/. For example:

requests.get('<https://rearc.secoda.co/api/v1/table/tables/>', headers={'Authorization': 'Bearer <token>'})

This worked, thank you both