This chapter discusses the essential Element mechanism, classification, and features. Filtering - Filtering is used to get a set of elements from the document. Selection - Working with the set of selected elements in a document. Parameters s - Most Element information is stored as Parameters.
This chapter discusses Parameter functionality. Elements are introduced based on element classification. Make sure that you read the Elements Essentials and Parameter chapters before reading about the individual elements. Editing Elements - Learn how to move, rotate, delete, mirror, group, and array elements. Family Instances - Learn about the relationship between family and family instance, family and family instance features, and how to load or create them.
Family Creation - Learn about creation and modification of Revit Family documents. Conceptual Design - Discusses how to create complex geometry and forms in a Revit Conceptual Mass document.
Datum and Information Elements - Learn how to set up grids, add levels, use design options, and more. Annotation Elements - Discusses document annotation including adding dimensions, detail curves, tags, and annotation symbols. Views - Learn about the different ways to view models and components and how to manipulate the view in the API. Material - Material data is an Element that identifies the physical materials used in the project as well as texture, color, and more.
Geometry - Discusses graphics-related types in the API used to describe the graphical representation of the model including the three classes that describe and store the geometry information. Place and Locations - Defines the project location including city, country, latitude, and longitude.
Shared Parameters s - Shared parameters are external text files containing parameter specifications. Transactions - Introduces the two uses for Transaction and the limits that you must consider when using Transaction. We will give you new credentials and consult on how to take care of them. Third-party services may be paid via Intento the default scenario or via your own account at the third party service. In order to use your own account at the third party service, specify the account credentials as described below.
NOTE: some of the services are available only with your own accounts i. We use the token-based authentication. Each request to intento API should pass an access key in header apikey as demonstrated in the examples below. For each account, we provide two keys, a real key and a sandbox one. Requests performed with the real key are actually fulfilled via third-party services and billed towards your account.
Usage limits for real keys are governed by the subscription tier you have. Requests performed with the sandbox key are intended for testing purposes and return some sample responses.
Usage limits for sandbox keys are quite low, let us know if anything is wrong with that. Actual data processing limits depend on the subscription plan and the technical limitations of the selected third-party services. In case if your request exceeds limits you can use the async mode. The current approach to handling the oversized requests is described in a separate document. Error responses usually include a JSON document in the response body, which contains information about the error.
In async mode , response also includes a specific position of the error. Specify the source text, the target language and the desired translation provider in JSON body of the request as in the following example:.
Proceed to the following links for more details and examples on how to use a particular intent. If the server responded with a status of Request Entity Too Large , then the request data is too large for the synchronous processing. In this case, you should switch to the asynchronous mode by setting service. Wait for processing to complete. TTL of the resource is 30 days.
If the operation is not completed the value of done is false. Wait and make request later. If the operation encountered an error during fulfillment, you would see a response with partial result and error. This result contains successfully fulfilled elements of the initial request and nulls where the error occurred. More information about the cause of the problem you can find in an error object.
The object contains a list of failed requests with corresponding error responses. For more convenient mapping there is an item key and a position key in the object.
The item key is an index of the element in the initial request array. And the position key is an index of the element in the sub-array. Here is an example of the operation which failed:. Intento do not keep payload in logs, but in some cases it may be useful for debugging. Saving data in logs can be controlled using the boolean flag trace. If flag do not set or set false we do not keep user payload in logs. Flag name is case insensitive.
In the tech proxy mode, the custom credentials are passed in the auth service field. For each ID specify your own key s you want to use and values set to a list of keys for the specified provider.
There could be more than one key for the provider in the case you want to work with a pool of keys more on this advanced feature later. Auth object structure is different for different providers and may be obtained together with other provider details by sending GET request for this provider:. So it imposes some extra work when using your own credentials — you have to regenerate these temporary credentials by yourself and provide them with each request to Intento.
You have to know when you need to regenerate a token, or we let you know when we cannot fulfill a request using a provided token because it was expired , so you can catch this situation, regenerate a token by yourself and continue using Intento API. It is not very handy, because some tokens expire just after an hour, so you have to regenerate them each hour. Even if this process can be automated it takes much extra work: you need to catch this particular situation, regenerate a token, resend a bunch of requests which happen to be called with the expired token.
The situation becomes harder when you run large async jobs that could take more time than a token lifetime. In this situation a part of such request will fail, so you need to split your requests into smaller parts or resubmit failed tasks with a new token.
It is painful. We provide a much more convenient and hassle-free way to work with temporary credentials. You can provide us with all the required information to generate temporary tokens. Another option is to delegate us the required credentials through the API , and we take care of the whole process, automatically regenerating tokens when it's needed and substituting an actual token in the request to a provider.
You pass a credential id which is constant now , and we do all the job with translating it to always-working tokens. Here is the instruction on how to connect your accounts of different providers. Right now this mode is supported for ai. Intento provides the smart routing feature, so that the translation request is automatically routed to the best provider. The best provider is determined based on the following information:. This behavior may be controlled by specifying the desired routing strategy in the service.
Contact us at hello inten. Both for smart routing mode and basic mode, a failover is supported.
0コメント