Automate Cambase.io
HumDay reads Cambase.io’s own published API description and derives 17 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Cambase.io is
Cambase.io is a project by Evercam.io in order to make it easier for software developers to have a reliable, up to date source of model hardware information available via a public API.
API host: api.cambase.io
What HumDay can do in Cambase.io
9 documented operations change something in Cambase.io.
- POSTCreates a new Model
/api/v1/models.json - POSTCreates a new Vendor
/api/v1/vendors.json - POSTCreates a new Recorder
/api/v1/recorders.json - PATCHUpdates an existing Model
/api/v1/models/{id}.json - PUTUpdates an existing Model
/api/v1/models/{id}.json - PATCHUpdates an existing Vendor
/api/v1/vendors/{id}.json - PUTUpdates an existing Vendor
/api/v1/vendors/{id}.json - PATCHUpdates an existing Recorder
/api/v1/recorders/{id}.json - PUTUpdates an existing Recorder
/api/v1/recorders/{id}.json
What HumDay can read from Cambase.io
These are the operations a schedule or a trigger can watch.
- GETSearches all Models
/api/v1/models/search.json - GETSearches all Recorders
/api/v1/recorders/search.json - GETFetches all Models
/api/v1/models.json - GETFetches all Vendors
/api/v1/vendors.json - GETFetches all Recorders
/api/v1/recorders.json - GETFetches a single Model
/api/v1/models/{id}.json - GETFetches a single Vendor
/api/v1/vendors/{id}.json - GETFetches a single Recorder
/api/v1/recorders/{id}.json
How automating Cambase.io works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Cambase.io account.
- Grant access, then go live. You approve the specific Cambase.io operations it may use — and only those.
Questions about Cambase.io automation
- Can HumDay connect to Cambase.io?
- Yes. HumDay reads Cambase.io's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 17 operations are documented.
- Do I need to write code to automate Cambase.io?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Cambase.io account.
- What can HumDay do in Cambase.io?
- 9 of the 17 documented operations change something in Cambase.io, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Cambase.io account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Cambase.io is held behind that approval.
Where this came from
The operations above are read from a published API description for Cambase.io at api.cambase.io/api-docs/api-docs.json. Descriptions are the provider’s own words, not ours. Last published 2018-12-31.