mz2
1
I’m trying to reach the eventing API described at https://developer.couchbase.com/documentation/server/5.5/eventing/eventing-api.html to automate depositing functions to the server. My Couchbase Server’s HTTP listener that responds to other REST API calls successfully is at http://localhost:8091.
- Tried GET at http://localhost:8091/api/v1/functions with correct basic auth details
- Tried POST to localhost:8091/api/v1/functions/foo with correct basic auth details and an “application/json” typed body
In both cases “resource not found” (404). What am I doing wrong?
mz2
2
… and I should note, the eventing service is enabled and I’m able to create and edit functions from the web UI.
mz2
3
Answering my own question, after digging around source code a bit I realised the documentation examples given at https://developer.couchbase.com/documentation/server/5.5/eventing/eventing-api.html are inaccurate and that the port for the eventing admin REST API is at 8096.
asingh
4
Hi Matias,
Thanks a lot for catching documentation bug. I’ve requested doc team to address it - DOC-3938.
I hope you’re able to leverage REST endpoints correctly after switching to port 8096. If not, please let me know.
Additionally if you could share some details about your use case for Eventing, it would be useful for us.
Thanks,
Abhishek