Back to Collection Items
; This example assumes the Chilkat API to have been previously unlocked.
; See Global Unlock Sample for sample code.
$oHttp = ObjCreate("Chilkat.Http")
Local $bSuccess
; Use this online tool to generate code from sample JSON: Generate Code to Create JSON
; The following JSON is sent in the request body.
; {
; "name": "",
; "script": "",
; "order": {},
; "enabled": true,
; "stage": ""
; }
$oJson = ObjCreate("Chilkat.JsonObject")
$oJson.UpdateString("name","")
$oJson.UpdateString("script","")
$oJson.UpdateNewObject("order")
$oJson.UpdateBool("enabled",True)
$oJson.UpdateString("stage","")
; Adds the "Authorization: Bearer {{auth0_token}}" header.
$oHttp.AuthToken = "{{auth0_token}}"
$oHttp.SetRequestHeader "Content-Type","application/json"
Local $oResp = $oHttp.PostJson3("https://{{auth0_domain}}/api/v2/rules","application/json",$oJson)
If ($oHttp.LastMethodSuccess = False) Then
ConsoleWrite($oHttp.LastErrorText & @CRLF)
Exit
EndIf
ConsoleWrite($oResp.StatusCode & @CRLF)
ConsoleWrite($oResp.BodyStr & @CRLF)
Curl Command
curl -X POST
-H "Authorization: Bearer {{auth0_token}}"
-H "Content-Type: application/json"
-d '{
"name": "",
"script": "",
"order": {},
"enabled": true,
"stage": ""
}'
https://{{auth0_domain}}/api/v2/rules
Postman Collection Item JSON
{
"name": "Create a rule",
"request": {
"method": "POST",
"header": [
{
"key": "Authorization",
"value": "Bearer {{auth0_token}}"
},
{
"key": "Content-Type",
"value": "application/json"
}
],
"body": {
"mode": "raw",
"raw": "{\r\n \"name\": \"\",\r\n \"script\": \"\",\r\n \"order\": {},\r\n \"enabled\": true,\r\n \"stage\": \"\"\r\n}"
},
"url": {
"raw": "https://{{auth0_domain}}/api/v2/rules",
"protocol": "https",
"host": [
"{{auth0_domain}}"
],
"path": [
"api",
"v2",
"rules"
]
},
"description": "Creates a new rule according to the JSON object received in <code>body</code>.<br/>The samples on the right show you every attribute that could be used. Mandatory attributes are <code>name</code> and <code>script</code>Note: Changing a rule's stage of execution from the default <code>login_success</code> can change the rule's function signature to have user omitted."
},
"response": [
]
}