Automate VisageCloud
HumDay reads VisageCloud’s own published API description and derives 42 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 VisageCloud is
Face search, recognition & classification API. Just make a call to our REST API each time your app needs to access face recognition and classification capabilities.
API host: visagecloud.com
What HumDay can do in VisageCloud
23 documented operations change something in VisageCloud.
- POSTCreate new empty collection with given name
/rest/v1.1/collection/ - POSTAdds (maps) a list of faces, identified by faceHashes, to a profile, identified by profileId
/rest/v1.1/profile/map - POSTCreate new stream with given name
/rest/v1.1/stream/stream - POSTCreate new SVM classifier with given name
/rest/v1.1/classifier/svm - POSTCreates a new profile with no faces associated to it (empty profile)
/rest/v1.1/profile/profile - DELETERemoves (unmaps) a list of faces, identified by faceHashes, from a profile, identified by profileId
/rest/v1.1/profile/map - POSTGet account information including accessKey and secretKey by email and password
/rest/v1.1/account/login - PATCHStop existing stream
/rest/v1.1/stream/stop - PATCHStart existing stream
/rest/v1.1/stream/start - DELETEDelete existing classifier
/rest/v1.1/classifier/svm - PATCHCleanup frames older than specified timeframe
/rest/v1.1/stream/cleanup - POSTPerform detection on a given picture or picture URL
/rest/v1.1/analysis/detection - POSTCount individuals in streams or collections
/rest/v1.1/analytics/counting - POSTPerform labeled recognition on a given picture or picture URL
/rest/v1.1/analysis/recognition - POSTChange password for an account using old password
/rest/v1.1/account/changePassword - DELETEDelete existing stream
/rest/v1.1/stream/{id} - DELETEDeletes a profile and unmaps all its faces
/rest/v1.1/profile/{id} - PATCHUpdate an existing profile with a given id
/rest/v1.1/profile/{id} - DELETEDelete existing collection with associated profiles and faces.
/rest/v1.1/collection/{id} - PATCHUpdate an existing collection with a given id
/rest/v1.1/collection/{id} - PATCHUpdate an existing stream with a given ID
/rest/v1.1/stream/{streamId} - POSTShow presence (based on number of occurences of each face) breakdown per declared attribute (age, gender)
/rest/v1.1/analytics/presence/total - POSTShow audience (based on number of occurrences of each person) breakdown per declared attribute (age, gender).
/rest/v1.1/analytics/presence/timeseries
What HumDay can read from VisageCloud
These are the operations a schedule or a trigger can watch.
- GETRetrieve all collections
/rest/v1.1/collection/ - GETShow status of all streams from account
/rest/v1.1/stream/all - GETGets all the faceHashes associated to a profile
/rest/v1.1/profile/map - GETGet last processed N frames from stream
/rest/v1.1/stream/frames - GETGet classifier full
/rest/v1.1/classifier/svm - GETGet account information by accessKey and secretKey
/rest/v1.1/account/account - GETCompare several faces identified by faceHash, without depending on mapping faces to profiles
/rest/v1.1/analysis/compare - GETRetrieve a complete analysis object including both detection and recognition information
/rest/v1.1/analysis/retrieve - GETGet last N recognized individuals from stream
/rest/v1.1/stream/attendance - GETGet individual frame image
/rest/v1.1/stream/frameImage - GETRetrieve the last count operations per current account
/rest/v1.1/analysis/listLatest - GETGets the enrollment status of a profile: information on whether it is suitable for authentication.
/rest/v1.1/profile/enrollmentStatus - GETRetrieves a profile
/rest/v1.1/profile/{id} - GETRetrieve existing collection content
/rest/v1.1/collection/{id} - GETGet an existing stream with a given ID
/rest/v1.1/stream/{streamId} - GETGet classifer status
/rest/v1.1/classifier/svm/status - GETRetrieve collection content for data analysis.
/rest/v1.1/collection/export/csv - GETGets all the profiles associated to a collection
/rest/v1.1/collection/{id}/profile - GETGet billing information by accessKey and secretKey
/rest/v1.1/account/billing
How automating VisageCloud 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 VisageCloud account.
- Grant access, then go live. You approve the specific VisageCloud operations it may use — and only those.
Automate VisageCloud with these
Categories
Questions about VisageCloud automation
- Can HumDay connect to VisageCloud?
- Yes. HumDay reads VisageCloud's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 42 operations are documented.
- Do I need to write code to automate VisageCloud?
- 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 VisageCloud account.
- What can HumDay do in VisageCloud?
- 23 of the 42 documented operations change something in VisageCloud, and 19 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my VisageCloud 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 VisageCloud is held behind that approval.
Where this came from
The operations above are read from a published API description for VisageCloud at visagecloud.com/v2/api-docs. Descriptions are the provider’s own words, not ours. Last published 2018-08-24.