PUT /api/v1/org
Replaces the Org General Settings for your Okta org
Servers
- https://{yourOktaDomain}
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
subdomain |
String | No |
Subdomain of org |
endUserSupportHelpURL |
String | No |
Support link of org |
address2 |
String | No |
Secondary address of the organization associated with the org |
phoneNumber |
String | No |
Phone number of the organization associated with the org |
address1 |
String | No |
Primary address of the organization associated with the org |
website |
String | No |
Website of the organization associated with the org |
status |
String | No |
Status of org Possible values:
|
state |
String | No |
State of the organization associated with the org |
city |
String | No |
City of the organization associated with the org |
lastUpdated |
String | No |
When org was last updated |
id |
String | No |
Org ID |
_links |
Object | No |
Specifies link relations (see Web Linking) available for the org using the JSON Hypertext Application Language specification |
companyName |
String | No |
Name of org |
postalCode |
String | No |
Postal code of the organization associated with the org |
created |
String | No |
When org was created |
expiresAt |
String | No |
Expiration of org |
supportPhoneNumber |
String | No |
Support help phone of the organization associated with the org |
country |
String | No |
County of the organization associated with the org |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.