Login to get token in Gitlab

What this operation does

Login to get token

• POSTChanges data · sessiongitlab.com/v3/session

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Gitlab operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Gitlab operations

• Add new email address to the currently authenticated userPOST · changes data
• Create a user. Available only for adminsPOST · changes data
• Add an email address to a specified userPOST · changes data
• Create a new project issuePOST · changes data
• Add a new SSH key to the currently authenticated userPOST · changes data
• Create new file in repositoryPOST · changes data
• Delete an email address of a specified userDELETE · changes data
• Create a new system hookPOST · changes data

All 358 Gitlab operations

Questions

Can HumDay login to get token in Gitlab?

Yes. This operation is published in Gitlab's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Gitlab data?

Yes — this is a POST operation, so it changes something in Gitlab. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Gitlab account.

Where this came from

Read from a published API description for Gitlab at axil.gitlab.io/swaggerapi/static/swagger.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.