CE-Go
Connect your client's CE-Go with a key they paste, and call its API through Operate As.
- Website
- ce-go.com
- Connects by
- Pasting a API key
- Category
- Calendars and meetings
- Services
- 1
- Tools
- Pass-through only
| Service | Key | Base URL |
|---|---|---|
| CE-Go | ce-go | https://app.ce-go.com/api/v3 |
Connecting
Your client makes a API key in their CE-Go settings and pastes it on their link. Operate As tries it with CE-Go before saving it, and stores it encrypted. See Services connected with an API key.
curl https://api.operate.as/v1/me/clients \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"[ { "id": "6f1c2a7e-...", "name": "Miller Dental", "services": [ "ce-go" ] }]Permissions
| What the client reads | Permission it asks for |
|---|---|
| Use the CE-Go key you paste, with only the access you gave that key | Chosen on the provider's screen |
Pass-through
CE-Go has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.
Add the client
In Clients, add your client and select CE-Go. Then send them their link.
Your client connects
They paste a API key from their CE-Go settings.
Find the endpoint
Pick the call from CE-Go's own API docs. Your path is everything after https://app.ce-go.com/api/v3.
Send it through Operate As
Use the client's ID, the service key ce-go and that path. Your Operate As key goes in Authorization; the client's access is added for you.
See Pass-through requests for the full request and response format.
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../ce-go/zapier/conferences" \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"{ "status": 200, "data": { "…": "the service's own response" }, "encoding": "json"}When access ends
A key works until your client deletes it in CE-Go. They can paste a new one on the same link at any time, and your workflows carry on without changes.
See Keeping access alive and Removing access.
{ "status": 401, "data": { "…": "the service's own error" }, "encoding": "json"}