API v2 - Explanation and valid values for some fields on Tenant and User entities. Accessibility of JSON schemas.

On API v2 there are some fields on the Tenant and User entities for which there's no explanation available or a list of valid values to put in them. Next, the list of those fields.
- Tenant:
- customer_type: explanation and possible values required.
- language: on this one I'd just like to know what type of locale ISO codes go there ("en" style, "en-US" style or maybe both?).
- owner_id: explanation required.
- internal_tag: explanation and possible values required.
- default_idp_id: explanation needed, specially because it always seems to be the same value (11111111-1111-1111-1111-111111111111).
- User:
- personal_tenant_id: explanation required.
- idp_id: the same comment as for default_idp_id in Tenant.
- language: the same comment as for language in Tenant.
- business_types: explanation and possible values required.
Related to this, I've noticed in the RAML documentation the mention to references of the json schemas for some fields like the ones I've listed before. For instance, I've read something like this:
"business_types": { "$ref": "../_common/types/business_types.json" }
That reference can be found in the request body schema of the User POST method. How could I access those json schemas?

Dmitry Zelensky wrote:However, I recommend to do the following when you are not sure which values to use for specific fields:
- Create the object via common interface (Web Console)
- Get the default values for these objects
- Replace only those values that you need. The rest should remain as default.
As for JSON schemas, AFAIK they are not available for public.
Hi,
Please don't take this the wrong way, but this is no way for any of us to develop an API to sell your products for you!
We really shouldn't have to be prodding and poking the system to try and find the values we need, it should be properly documented. It's incredibly frustrating having to guess at everything, especially with APIv2 and makes everything take 10x longer than it should.
At the end of the day, we're here because we want to help sell your products and make you and us some money, you really should be making a better job of facilitating that with your API and documentation. If the API is expecting values from us, we should know the schema for those values
- if it's private, then it shouldn't be in the API and exposed at all.
- if it's essential to make it work, then it should be documented and available to us.
Apologies for digging an old thread, but given this one was asking for the same information that I'm trying to find, it seems appropriate.
Thanks,
Karl
- Log in to post comments

Dear Karl,
thank you for taking the time to share your feedback on API documentation, I've passed it to the product management. Currently, we're working on the more detailed doc that is expected to become available with the next major product release.
- Log in to post comments
Best regards,
Ekaterina Surkova | Forum Moderator
Information provided AS-IS with no warranty of any kind.
To contact support, please follow http://www.acronis.com/en-us/support

Dear Karl,
We opened API and create documentation. You can find detailed descriptions for Account Management API here https://developer.acronis.com/doc/platform/management/v2/#/http/getting-started
For example, for tenant JSON values here https://developer.acronis.com/doc/platform/management/v2/#/http/models/structures/tenant-post
- Log in to post comments
Stas Pavlov | Technology Evangelist
Acronis Developer Network | Acronis Cyber Cloud Solutions Portal | Acronis Cyber Platform
For more answers to your questions, try our Knowledge Base and Video Tutorials
Our mission is to create Customers and Partners success. Our management team welcomes your comments and suggestions on how we can improve the overall support we provide to you. Please send your comments, suggestions, or concerns to Managers or submit your feedback here.
Dmitry Zelensky | Product Manager
Acronis Customer Central | Acronis Backup Software
For more answers to your questions, try our Knowledge Base and Video Tutorials
Our mission is to create Customer success. Our management team welcomes your comments and suggestions on how we can improve the overall support we provide to you. Please send your comments, suggestions, or concerns to Managers or submit your feedback here.