-
Notifications
You must be signed in to change notification settings - Fork 442
Admin API
Paula Gombar edited this page Sep 3, 2021
·
6 revisions
Since this API is exposed by the runtime, the base URL is: https://<functionappname>.azurewebsites.net/
. Hitting the URLs require the functions' master key to be passed in the header as x-functions-key
.
GET /admin/host/status/
Response:
{
"id": "bad1ecf31b47-2137340777",
"state": "Running",
"version": "2.0.1.0",
"versionDetails": "2.0.1.0-beta1 Commit hash: N/A"
}
POST /admin/host/status/
Response: empty body
POST /admin/host/logs/
[
{
"Level": 2,
"FunctionName": "MyFunc",
"Source": "runtime",
"Message": "Some Message"
}
]
Response: empty body
POST /admin/host/synctriggers/
Response: empty body
PUT /admin/function/{function_name}
Response: 201 (Created) if successful, 400 for bad requests (function name invalid or app in read-only mode), 500 if failed to create
- Configuration Settings
- function.json
- host.json
- host.json (v2)
- Http Functions
- Function Runtime Versioning
- Official Functions developers guide
- Host Health Monitor
- Managing Connections
- Renaming a Function
- Retrieving information about the currently running function
- Site Extension Resolution
- Linux Consumption Regions
- Using LinuxFxVersion for Linux Function apps
- Out-of-proc Cancellation Tokens
- Assembly Resolution in Azure Functions
- ILogger
- Precompiled functions
- Official Functions C# developer reference
- Contributor Onboarding
- Development Process
- Deploying the Functions runtime as a private site extension
- Authoring & Testing Language Extensions
- Bindings in out-of-proc
- Language Extensibility
- Worker Capabilities
- Investigating and reporting issues with timer triggered functions not firing
- Sharing Your Function App name privately
- Azure Functions CLI release notes [moved here]
- Function App Zipped Deployment [deprecated]