Automate Azurewebsites

What Azurewebsites is

Web API for TL mobile and web app

API host: tl-api.azurewebsites.net

What HumDay can do in Azurewebsites

14 documented operations change something in Azurewebsites.

• POSTAdd new article/api/Article
• POSTAdd new Member/api/Membership
• POSTRegister a new User/api/User/registerUser
• POSTInsert new package into the system/api/Package
• PUTUpdate an exsisting User/api/User/updateuser
• POSTAdd measure unit/api/Article/MeasureUnit
• PUTAdd article details that associate with a Gym/api/Article/ArticleGymDetails
• DELETEDelete article from the system/api/Article
• PUTupdate existing article/api/Article
• DELETEDelete existing package/api/Package
• PUTUpdate existing package by its ID/api/Package
• POSTAuthenticate and provide token for autherizations./api/Auth/login
• PUTDeactivate existing article/api/Article/UpdateStatus
• PUTStatus update of existing package/api/Package/UpdateStatus

What HumDay can read from Azurewebsites

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

• GETGet all Users detail This will return all properties related to User entity/api/User
• GETGet the current status of message/api/Status
• GETSearch articles It will only return basic information of article/api/Article/Search
• GETSearch packages/api/Package/Search
• GETGet the all Test objects./api/Test
• GETGet package details by packageId/api/Package
• GETGet all of the members details This will return all properties related to member entity/api/Membership
• GETGet mesure units/api/Article/MeasureUnits
• GETGet Revenue Accounts/api/Article/RevenueAccounts
• GETGet gym details This will return all properties related to gym entity/api/Gym/{gymID}
• GETGet article details This will return all properties related to article entity/api/Article/{articleID}
• GETGet Gym specific properties for article/api/Article/GymArticle/{articleId}/{gymId}
• GETRead GetAddons/api/Article/GetAddons

How automating Azurewebsites works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. 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.
3. See it proven. The program runs and shows you the result before it is allowed near your live Azurewebsites account.
4. Grant access, then go live. You approve the specific Azurewebsites operations it may use — and only those.

Popular Azurewebsites integrations

Connect Azurewebsites to the tools people pair it with most.

• Azurewebsites and OData for namespace microsoft.graphintegration
• Azurewebsites and Cloudflareintegration
• Azurewebsites and NetBoxintegration
• Azurewebsites and GitHubintegration
• Azurewebsites and Mistintegration
• Azurewebsites and Loket.nlintegration
• Azurewebsites and Atlassian The Jira Cloud platformintegration
• Azurewebsites and Magento B2Bintegration
• Azurewebsites and Stripeintegration
• Azurewebsites and Zuora Reference Billingintegration
• Azurewebsites and bunqintegration
• Azurewebsites and DocuSignintegration

Automate Azurewebsites with these

• Azurewebsites Documentation2 operations

Questions about Azurewebsites automation

Can HumDay connect to Azurewebsites?

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

Do I need to write code to automate Azurewebsites?

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 Azurewebsites account.

What can HumDay do in Azurewebsites?

14 of the 27 documented operations change something in Azurewebsites, and 13 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Where this came from

The operations above are read from a published API description for Azurewebsites at tl-api.azurewebsites.net/swagger/default/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2020-08-10.