One or more event types, such as system.api_token.create, user.session.start, user.account.reset_password. The full listing/catalog of event types is available here.

Note: if the event-type list contains any event types that are invalid, Okta will prevent you from turning on this Zap.

API docs for Okta are located here https://developer.okta.com/docs/reference/

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.

This is the name the user will log in with. This should be a unique value in your system. By default, we'll use the value in the Email field.