Get organization
GET/bv/org/v1/organizations
Fetches the details of an organization using the provided access token.
- Returns a
404
/NotFound
error if the specified resource is not found.
Responses
- 200
- 400
- 401
- 403
- 500
- default
A successful response.
- application/json
- Schema
- Example (from schema)
Schema
organization object
Output only. The resource identifier of the organization.
Output only. The name of the organization.
Output only. The appended parent organization id.
Possible values: [ORGANIZATION_TYPE_ROOT
, ORGANIZATION_TYPE_GENERAL_DISTRIBUTOR
, ORGANIZATION_TYPE_RESELLER
, ORGANIZATION_TYPE_BUSINESS
]
Output only. Indicates the type of the organization.
Possible values: [ORGANIZATION_STATUS_ACTIVATED
, ORGANIZATION_STATUS_VERIFYING
, ORGANIZATION_STATUS_FAIL_TO_VERIFY
, ORGANIZATION_STATUS_DEACTIVATED
, ORGANIZATION_STATUS_DELETING
, ORGANIZATION_STATUS_DELETED
, ORGANIZATION_STATUS_ACTIVATION_SCHEDULED
]
Output only. Indicates the status of the organization.
Output only. The description of the organization.
Output only. The owner email of the organization.
Output only. The billing cycle of the organization.
Output only. The contract valid start day won't be valid before the day.
Output only. The contract duration unit. It might one of the contract_months
or contract_days
.
Output only. The contract duration unit. It might one of the contract_months
or contract_days
.
Output only. The contract valid end day won't be valid after the day.
next_contract object
Output only. The next contract of the organization.
Output only. The start time of the organization.
Output only. The months of the organization.
Output only. The days of the organization.
Output only. The valid end time of the organization.
Output only. The parent id of the organization.
Output only. The plan id of the organization.
Output only. Indicates there are sub-organizations appended to the organization.
Output only. The name of appended parent organization.
Output only.
Output only. The time zone of the organization.
owner object
Output only. The unique id of the user.
Output only. The email of the user.
Possible values: [ACCOUNT_STATUS_ACTIVATED
, ACCOUNT_STATUS_DEACTIVATED
]
Output only. The status of the user.
Possible values: [ROLE_TYPE_OWNER
, ROLE_TYPE_ADMIN
, ROLE_TYPE_STAFF
, ROLE_TYPE_DEVELOPER
, ROLE_TYPE_CONTENT_CONTRIBUTOR
, ROLE_TYPE_CUSTOM
]
Output only. The role of the user.
Output only. The created time of the user.
Output only. The first name of the user.
Output only. The last name of the user.
Output only.
Output only.
{
"organization": {
"id": "string",
"name": "string",
"parent_id": "string",
"type": "ORGANIZATION_TYPE_ROOT",
"status": "ORGANIZATION_STATUS_ACTIVATED",
"description": "string",
"owner_email": "string",
"billing_cycle": 0,
"contract_valid_start_time": "2024-07-29T15:51:28.071Z",
"contract_months": 0,
"contract_days": 0,
"contract_valid_end_time": "2024-07-29T15:51:28.071Z",
"next_contract": {
"start_time": "2024-07-29T15:51:28.071Z",
"months": 0,
"days": 0,
"end_time": "2024-07-29T15:51:28.071Z",
"parent_id": "string",
"plan_id": "string"
},
"has_sub_orgs": true,
"parent_name": "string",
"license_key": "string",
"time_zone": "string",
"owner": {
"id": "string",
"email": "string",
"status": "ACCOUNT_STATUS_ACTIVATED",
"role_type": "ROLE_TYPE_OWNER",
"created_at": "2024-07-29T15:51:28.071Z",
"first_name": "string",
"last_name": "string"
},
"created_at": "2024-07-29T15:51:28.071Z",
"updated_at": "2024-07-29T15:51:28.071Z"
}
}
A bad request response.
The code
is 3
means got an invalid argument. There are more HTTP status code mappings listed on here and gRPC code on here.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- If no scheme is provided,
https
is assumed. - An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
- Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
- ]
details object[]
A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form
(e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme http
, https
, or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.
Schemes other than http
, https
(or the empty scheme) might be
used with implementation specific semantics.
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}
A unauthenticated response.
The header authorization
was missing or unidentified.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- If no scheme is provided,
https
is assumed. - An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
- Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
- ]
details object[]
A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form
(e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme http
, https
, or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.
Schemes other than http
, https
(or the empty scheme) might be
used with implementation specific semantics.
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}
A forbidden response.
It means that the provided authorization
did not have enough permission to access the resource or the API.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- If no scheme is provided,
https
is assumed. - An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
- Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
- ]
details object[]
A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form
(e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme http
, https
, or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.
Schemes other than http
, https
(or the empty scheme) might be
used with implementation specific semantics.
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}
A server error response. There are more HTTP status code mappings listed on here.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- If no scheme is provided,
https
is assumed. - An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
- Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
- ]
details object[]
A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form
(e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme http
, https
, or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.
Schemes other than http
, https
(or the empty scheme) might be
used with implementation specific semantics.
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}
An unexpected error response.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- If no scheme is provided,
https
is assumed. - An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
- Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
- ]
details object[]
A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form
(e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme http
, https
, or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.
Schemes other than http
, https
(or the empty scheme) might be
used with implementation specific semantics.
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}