Package ai.extend

Class RawExtendClient

  • public class RawExtendClient
extends java.lang.Object

    • Constructor Detail

      • RawExtendClient

        public RawExtendClient​(ClientOptions clientOptions)

    • Method Detail

      • parse

        public ExtendClientHttpResponse<ParseRun> parse​(ParseRequest request)
        Parse a file synchronously, waiting for the result before returning. This endpoint has a 5-minute timeout — if processing takes longer, the request will fail.

        Note: This endpoint is intended for onboarding and testing only. For production workloads, use POST /parse_runs with webhooks or polling instead, as it provides better reliability for large files and avoids timeout issues.

        The Parse endpoint allows you to convert documents into structured, machine-readable formats with fine-grained control over the parsing process. This endpoint is ideal for extracting cleaned document content to be used as context for downstream processing, e.g. RAG pipelines, custom ingestion pipelines, embeddings classification, etc.

        For more details, see the Parse File guide.

      • parse

        public ExtendClientHttpResponse<ParseRun> parse​(ParseRequest request,
                                                RequestOptions requestOptions)
        Parse a file synchronously, waiting for the result before returning. This endpoint has a 5-minute timeout — if processing takes longer, the request will fail.

        Note: This endpoint is intended for onboarding and testing only. For production workloads, use POST /parse_runs with webhooks or polling instead, as it provides better reliability for large files and avoids timeout issues.

        The Parse endpoint allows you to convert documents into structured, machine-readable formats with fine-grained control over the parsing process. This endpoint is ideal for extracting cleaned document content to be used as context for downstream processing, e.g. RAG pipelines, custom ingestion pipelines, embeddings classification, etc.

        For more details, see the Parse File guide.

      • edit

        public ExtendClientHttpResponse<EditRun> edit​(EditRequest request)
        Edit a file synchronously, waiting for the result before returning. This endpoint has a 5-minute timeout — if processing takes longer, the request will fail.

        Note: This endpoint is intended for onboarding and testing only. For production workloads, use POST /edit_runs with webhooks or polling instead, as it provides better reliability for large files and avoids timeout issues.

        The Edit endpoint allows you to detect and fill form fields in PDF documents.

        For more details, see the Edit File guide.

      • edit

        public ExtendClientHttpResponse<EditRun> edit​(EditRequest request,
                                              RequestOptions requestOptions)
        Edit a file synchronously, waiting for the result before returning. This endpoint has a 5-minute timeout — if processing takes longer, the request will fail.

        Note: This endpoint is intended for onboarding and testing only. For production workloads, use POST /edit_runs with webhooks or polling instead, as it provides better reliability for large files and avoids timeout issues.

        The Edit endpoint allows you to detect and fill form fields in PDF documents.

        For more details, see the Edit File guide.

      • extract

        public ExtendClientHttpResponse<ExtractRun> extract​(ExtractRequest request)
        Extract structured data from a file synchronously, waiting for the result before returning. This endpoint has a 5-minute timeout — if processing takes longer, the request will fail.

        Note: This endpoint is intended for onboarding and testing only. For production workloads, use POST /extract_runs with webhooks or polling instead, as it provides better reliability for large files and avoids timeout issues.

        The Extract endpoint allows you to extract structured data from files using an existing extractor or an inline configuration.

        For more details, see the Extract File guide.

      • extract

        public ExtendClientHttpResponse<ExtractRun> extract​(ExtractRequest request,
                                                    RequestOptions requestOptions)
        Extract structured data from a file synchronously, waiting for the result before returning. This endpoint has a 5-minute timeout — if processing takes longer, the request will fail.

        Note: This endpoint is intended for onboarding and testing only. For production workloads, use POST /extract_runs with webhooks or polling instead, as it provides better reliability for large files and avoids timeout issues.

        The Extract endpoint allows you to extract structured data from files using an existing extractor or an inline configuration.

        For more details, see the Extract File guide.

      • classify

        public ExtendClientHttpResponse<ClassifyRun> classify​(ClassifyRequest request)
        Classify a document synchronously, waiting for the result before returning. This endpoint has a 5-minute timeout — if processing takes longer, the request will fail.

        Note: This endpoint is intended for onboarding and testing only. For production workloads, use POST /classify_runs with webhooks or polling instead, as it provides better reliability for large files and avoids timeout issues.

        The Classify endpoint allows you to classify documents using an existing classifier or an inline configuration.

        For more details, see the Classify File guide.

      • classify

        public ExtendClientHttpResponse<ClassifyRun> classify​(ClassifyRequest request,
                                                      RequestOptions requestOptions)
        Classify a document synchronously, waiting for the result before returning. This endpoint has a 5-minute timeout — if processing takes longer, the request will fail.

        Note: This endpoint is intended for onboarding and testing only. For production workloads, use POST /classify_runs with webhooks or polling instead, as it provides better reliability for large files and avoids timeout issues.

        The Classify endpoint allows you to classify documents using an existing classifier or an inline configuration.

        For more details, see the Classify File guide.

      • split

        public ExtendClientHttpResponse<SplitRun> split​(SplitRequest request)
        Split a document synchronously, waiting for the result before returning. This endpoint has a 5-minute timeout — if processing takes longer, the request will fail.

        Note: This endpoint is intended for onboarding and testing only. For production workloads, use POST /split_runs with webhooks or polling instead, as it provides better reliability for large files and avoids timeout issues.

        The Split endpoint allows you to split documents into multiple parts using an existing splitter or an inline configuration.

        For more details, see the Split File guide.

      • split

        public ExtendClientHttpResponse<SplitRun> split​(SplitRequest request,
                                                RequestOptions requestOptions)
        Split a document synchronously, waiting for the result before returning. This endpoint has a 5-minute timeout — if processing takes longer, the request will fail.

        Note: This endpoint is intended for onboarding and testing only. For production workloads, use POST /split_runs with webhooks or polling instead, as it provides better reliability for large files and avoids timeout issues.

        The Split endpoint allows you to split documents into multiple parts using an existing splitter or an inline configuration.

        For more details, see the Split File guide.