Connect Figshare and Gettyimages Getty Images
Describe what you want to happen between Figshare and Gettyimages Getty Images in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
Figshare
136 documented operations. See all Figshare operations
- POSTCreate new Article
/account/articles - POSTCreate new Institution Account
/account/institution/accounts - POSTPOST Institution Curation Review Comment
/account/institution/review/{curation_id}/comments - POSTPublic Articles Search
/articles/search - POSTPublic Projects Search
/projects/search - POSTCreate project
/account/projects
Gettyimages Getty Images
52 documented operations. See all Gettyimages Getty Images operations
- POSTCreate a new board
/v3/boards - POSTAdd a comment to a board
/v3/boards/{board_id}/comments - PUTUpload image for use by the search creative images/videos operations
/v3/search/by-image/uploads/{file-name} - DELETEDelete a comment from a board
/v3/boards/{board_id}/comments/{comment_id} - PUTAdd assets to a board
/v3/boards/{board_id}/assets - PUTGet asset change notifications
/v3/asset-changes/change-sets
How a Figshare and Gettyimages Getty Images automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in Figshare and Gettyimages Getty Images, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- Figshare and OData for namespace microsoft.graph11,548 operations
- Gettyimages Getty Images and OData for namespace microsoft.graph11,464 operations
- Cloudflare and Figshare3,258 operations
- Cloudflare and Gettyimages Getty Images3,174 operations
- Figshare and NetBox980 operations
- Gettyimages Getty Images and NetBox896 operations
- Figshare and GitHub947 operations
- Gettyimages Getty Images and GitHub863 operations
- Figshare and Mist904 operations
- Gettyimages Getty Images and Mist820 operations
Questions about connecting Figshare and Gettyimages Getty Images
- Can Figshare connect with Gettyimages Getty Images?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect Figshare to Gettyimages Getty Images?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate Figshare and Gettyimages Getty Images?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across Figshare and Gettyimages Getty Images?
- Figshare publishes 136 documented operations and Gettyimages Getty Images publishes 52. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either Figshare or Gettyimages Getty Images is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Figshare and Gettyimages Getty Images. Descriptions are each provider’s own words, not ours.