I have had an endpoint on RunKit for over a year now, maybe even two years, built using the Express endpoint helper.
The other day I updated the code and republished the notebook, and now the endpoint is completely inaccessible, and I am getting an error that endpoints aren’t being exported. They are—I did not change the express server/endpoint part of the notebook, only some aspects of private functions on the back end. On top of this, the endpoint logs show that the endpoint is indeed being contacted and returning the correct data. It’s only on the client side that the endpoint is being blocked with the message ‘Endpoint is not being exported’. I am at a loss here for what to do.
The endpoint is for a Google PlusCode/Open Location Code conversion service, and two endpoints are exported,
encode endpoint takes a URL parameter of comma-separated latitude and longitude (e.g.
decode endpoint either takes only a URL parameter with a fully-formed Google PlusCode/Open Location Code (e.g.
/decode/6P8RCCFW) or a ‘Short Code’ form of a Google Plus/Open Location Code with an additional required
q query parameter for the region in which to query for the Short Code. (e.g.
/decode/CCFW+6P4?q=Lahore, Pakistan). Obviously all parameters should be URI-encoded before hitting the endpoint.