Org Rate Limit Violation
Triggers a flow when an organization-wide rate limit is exceeded in Okta.
|Date and Time
|Date and time the event was triggered in Okta API.
|Message details about the event.
|Event's unique identifier key.
|Type of event that was published.
|Timestamp when the notification was delivered to the service.
|ID of the Okta actor who triggered the org rate limit violation.
|Email address of the Okta actor.
|Display name of the Okta actor.
|Type of data returned.
|ID of the endpoint where the org rate limit violation was triggered.
|Type of the endpoint where the org rate limit violation was triggered.
|Webhook event's universal unique identifier.
|Raw JSON payload returned from the Okta API for this particular event.
|Object representing the headers for the response; each key of the header will be parsed into a header string as "key: value" (
|Source of user-specific data.
Information on the triggered event used for debugging.
For example, returned data can include a URI, an SMS provider, or transaction ID.
While you can create additional user or group fields for an Okta event, the Okta API only returns values for four fields: ID, Alternate ID, Display Name, and Type.
No other fields are supported for users or groups, and data from such fields isn't returned by this event card.