HTTP API Integration Limitation - Any Workarounds Available?

Hi community!

I’m working on integrating an Electronic Shelf Label (ESL) system with Coda through their API. The challenge is that this API only supports HTTP (port 8082) and doesn’t have HTTPS available. I understand Coda’s security-first approach of only supporting HTTPS, but in this case, we’re dealing with a hardware vendor’s API that we can’t modify.

Current limitations:

  • ESL API endpoint: http://domain:8082/api/handle
  • No HTTPS support available from the vendor
  • Can’t modify the API endpoint
  • Hardware vendor has no immediate plans to implement HTTPS

I’ve considered using a proxy service but before implementing that workaround, I wanted to check:

  1. Is there any way to make Coda work with HTTP APIs?
  2. Are there any plans to support HTTP in specific cases?
  3. Has anyone faced a similar situation and found a solution?

Thanks for any insights!

Hi @exeinformatica_microsshop - Unfortunately it isn’t possible for a Pack to connect to an endpoint that doesn’t use HTTPS. This restriction exists for security reasons, and there is no ability to make exceptions.

You can work around this solution by spinning up your own web app that receives HTTPS requests from the Pack, and translates them into HTTP requests to the target endpoint. This comes with some more technical complexity and cost, but likely doesn’t involve that much code.

Thanks for answering, at the moment I’m doing it through googlesheets, and then I’ll also try with n8n. Greetings

1 Like