Can HumDay connect to Probely Developers?

Yes. HumDay reads Probely Developers's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 143 operations are documented.

Do I need to write code to automate Probely Developers?

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 Probely Developers account.

What can HumDay do in Probely Developers?

72 of the 143 documented operations change something in Probely Developers, and 71 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Probely Developers 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 Probely Developers is held behind that approval.

Automate Probely Developers

HumDay reads Probely Developers’s own published API description and derives 143 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 Probely Developers is

Probely is a Web Vulnerability Scanning suite for Agile Teams. It provides continuous scanning of your Web Applications and lets you efficiently manage the lifecycle of the vulnerabilities found, in a sleek and intuitive ~~web interface~~ API. ## Quick-Start ### Authentication To use the API, you first need to create a token (API Key). To create a token, select a target from the drop-down list, go

API host: api.probely.com

What HumDay can do in Probely Developers

72 documented operations change something in Probely Developers. The 52 most useful are listed here.

POSTCreate new account webhook/webhooks/
POSTCreate/Reactivate a user./users/
POSTCreate new target webhook/targets/{target_id}/webhooks/
POSTSend reset password email/reset/
POSTChange user password/profile/change_password/
DELETEDeactivate a user/users/{id}/
PATCHPartial update user/users/{id}/
PUTUpdate user/users/{id}/
DELETEDelete account webhook/webhooks/{id}/
PATCHPartial update account webhook/webhooks/{id}/
PUTUpdate account webhook/webhooks/{id}/
POSTCreate account API key/keys/
POSTCreate label/labels/
POSTCreate target/targets/
POSTReset password after asking for a reset (with the token sent by email)./setpassword/
POSTCreate new asset/targets/{target_id}/assets/
POSTCreate new scheduled scan/targets/{target_id}/scheduledscans/
POSTAuthenticate user/auth/obtain/
POSTReplace token with a new one/auth/refresh/
POSTList archived targets/targets/archived/
POSTEnterprise user authentication/enterprise/auth/obtain/
DELETEDelete target webhook/targets/{target_id}/webhooks/{id}/
PATCHPartial update target webhook/targets/{target_id}/webhooks/{id}/
PUTUpdate target webhook/targets/{target_id}/webhooks/{id}/
POSTCheck validity of password reset token/check/
POSTAvailable actions for the selected targets/target-actions/
POSTCreate target API key/targets/{target_id}/keys/
POSTRevoke a token/auth/revoke/
POSTVerify a token/auth/verify/
POSTArchive targets/targets/archive/
POSTActivate targets/targets/activate/
DELETEDelete account API key/keys/{id}/
DELETEDelete label/labels/{id}/
PATCHPartial update/labels/{id}/
PUTUpdate label/labels/{id}/
DELETEDelete target/targets/{id}/
PATCHPartial update target/targets/{id}/
PUTUpdate target/targets/{id}/
POSTEnterprise token revokation/enterprise/auth/revoke/
POSTEnterprise token verification/enterprise/auth/verify/
POSTEnterprise token refresh/enterprise/auth/refresh/
POSTStart a scan on the target/targets/{target_id}/scan_now/
PATCHUpdate slack integration data/targets/{target_id}/integrations/slack/
PUTUpdate slack integration data/targets/{target_id}/integrations/slack/
PATCHUpdate Jira Cloud target configuration/targets/{target_id}/integrations/jira-cloud/
PUTUpdate Jira Cloud target configuration/targets/{target_id}/integrations/jira-cloud/
DELETEDelete target API key/targets/{target_id}/keys/{id}/
PATCHUpdate Jira Server target configuration/targets/{target_id}/integrations/jira-server/
PUTUpdate Jira Server target configuration/targets/{target_id}/integrations/jira-server/
DELETEDelete asset/targets/{target_id}/assets/{id}/
PATCHPartial update assets/targets/{target_id}/assets/{id}/
PUTUpdate asset/targets/{target_id}/assets/{id}/

What HumDay can read from Probely Developers

These are the operations a schedule or a trigger can watch.

GETList users/users/
GETList account events/events/
GETUser data/profile/
GETList account webhooks/webhooks/
GETRetrieve user/users/{id}/
GETRetrieve account event/events/{id}/
GETRetrieve account webhook/webhooks/{id}/
GETList API keys allowed to operate on account/keys/
GETSubscription plans/plans/
GETList labels/labels/
GETList targets/targets/
GETList frameworks/frameworks/
GETList target events/targets/{target_id}/events/
GETList target webhooks/targets/{target_id}/webhooks/
GETList vulnerability definitions/vulnerability_definitions/
GETList scans for all targets/targets/all/scans/
GETRetrieve target event/targets/{target_id}/events/{id}/
GETRetrieve target webhook/targets/{target_id}/webhooks/{id}/
GETRetrieve account information/account/
GETIntegrations available and installed in the account/integrations/
GETList Jira Projects/integrations/jira-cloud/projects/
GETList Jira Projects/integrations/jira-server/projects/
GETList target specific API keys/targets/{target_id}/keys/
GETList scans/targets/{target_id}/scans/
GETList target's assets/targets/{target_id}/assets/
GETList target findings/targets/{target_id}/findings/
GETList scheduled scans/targets/{target_id}/scheduledscans/
GETList scheduled scans for all targets expanding recurrence/targets/all/scheduledscans/expanded/
GETRetrieve account API key/keys/{id}/
GETRetrieve framework/labels/{id}/
GETRetrieve target/targets/{id}/
GETRetrieve framework/frameworks/{id}/
GETScan page/targets/{target_id}/scans/retrieve_page/
GETList scheduled scans expanding recurrence/targets/{target_id}/scheduledscans/expanded/
GETTop 5 vulnerabilities (all targets)./targets/all/top_vulns/
GETRisk trend graph data (all targets)/targets/all/risk_trend/
GETRetrieve vulnerability definition/vulnerability_definitions/{id}/
GETSeverity trend graph data (all targets)/targets/all/severity_trend/
GETAverage fix time graph data (all targets)/targets/all/average_fix_time/
GETTargets with open vulnerabilities pie chart data/targets/all/needs_attention_pie/
GETTargets with open vulnerabilities/targets/all/needs_attention_top/
GETTop 5 vulnerabilities/targets/{target_id}/top_vulns/
GETRisk trend graph data/targets/{target_id}/risk_trend/
GETIntegrations available and installed for the target/targets/{target_id}/integrations/
GETSeverity trend graph data./targets/{target_id}/severity_trend/
GETScan endpoints file/targets/{target_id}/scans/{id}/endpoints/
GETAverage vulnerability trend graph data/targets/{target_id}/average_fix_time/
GETRetrieve project issue types/integrations/jira-cloud/projects/{project_id}/issue_types/

How automating Probely Developers 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 Probely Developers account.
Grant access, then go live. You approve the specific Probely Developers operations it may use — and only those.