Extracta.ai integration: operations for AI agents
Extracta.ai connects to Type.com as an integration. This page lists the 15 operations documented for Claude and Codex in Type.com: 5 read, 6 write, 4 destructive.
About Extracta.ai
Extracta.ai is an AI-powered platform that automates data extraction from various document types, including PDFs, images, and text files, without requiring prior training.
Categories: Analytics & Data, Documents & Forms
How to connect Extracta.ai to Type.com
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
15 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
Data extraction
- Read
View extraction
This endpoint retrieves the details of an extraction process previously defined in the system. By submitting the unique extractionId, you can obtain information such as the extraction name, language, options set, and the fields that are being extracted. This is useful for verifying the setup of your extraction template or for debugging purposes.
POST /api/v1/viewExtraction - Read
Get results
This endpoint retrieves the results for a specific batch of documents. By providing the extractionId and batchId, you can obtain the processed data or the current status of the batch, indicating whether the processing is complete or still in progress. When also providing the fileId, the endpoint filters the results to only that file. One alternative will be to use the Webhook to receive the data when its ready on your own server.
POST /api/v1/getBatchResults - Read
Get credits
This GET endpoint returns the current number of credits available on your account. Credits are consumed per page processed, where 1 credit = 1 page.
GET /api/v1/credits - Write
Create extraction
Initiates a new document extraction process. This endpoint allows you to define an extraction with specific fields, options, and configurations. Once created, you can use the returned extractionId to upload files for processing.
POST /api/v1/createExtraction - Write
Update extraction
Updates an existing document extraction process by modifying specified parameters within the extraction details.  Only the parameters included in the extractionDetails will be updated; any parameters not included will remain unchanged. Use this to efficiently adjust specific aspects of an extraction process without altering its overall configuration.
PATCH /api/v1/updateExtraction - Write
Upload Files
This endpoint enables users to upload files to a specified extraction. If a batchId is included in the request, the files will be added to that specific existing batch on the platform. It is important to ensure that the batchId already exists; otherwise, the upload will not be successful. If no batchId is provided in the request, a new batch will automatically be created for the files. Files must be uploaded using the multipart/form-data content type, which is suitable for uploading binary files (like documents and images).
POST /api/v1/uploadFiles - Destructive
Delete extraction
This endpoint enables the deletion of an entire extraction process, a specific batch within an extraction, or an individual file, depending on the parameters provided in the request body. The action is permanent and cannot be undone. * Providing only the extractionId results in the deletion of the entire extraction process along with all associated batches and files. * Specifying both extractionId and batchId deletes the specified batch and all files within it from the extraction. * Including extractionId, batchId, and fileId leads to the deletion of a specific file within a batch.
DELETE /api/v1/deleteExtraction
Document classification
- Read
Classification: View classification
This endpoint retrieves the details of a classification process previously defined in the system. By submitting the unique classificationId, you can obtain information such as the classification name, description, configured document types, associated keywords, and any linked extraction templates. This is useful for verifying your classification setup or for debugging and auditing purposes.
POST /api/v1/documentClassification/viewClassification - Read
Classification: Get results
This endpoint retrieves the classification results for a specific batch of documents. By providing the classificationId and batchId, you can obtain the predicted document types for each file in the batch,. Optionally, including a fileId will return results for that specific file only. This is useful for retrieving targeted results without querying the entire batch.
POST /api/v1/documentClassification/getResults - Write
Classification: Create classification
Initiates a new document classification process. This endpoint allows you to define a classification with a list of possible document types. Once created, you can use the returned classificationId to upload documents for type prediction.
POST /api/v1/documentClassification/createClassification - Write
Classification: Update classification
Updates an existing document classification process by modifying specific parameters within the classification details. This endpoint is useful for adjusting document types, keywords, or metadata without recreating the entire classification setup.
PATCH /api/v1/documentClassification/updateClassification - Write
Classification: Upload Files
This endpoint enables users to upload files to a specific document classification process. If a batchId is provided in the request, the uploaded files will be added to that existing batch. If batchId is omitted, a new batch will be automatically created for the files under the specified classificationId. Files must be uploaded using the multipart/form-data content type, which is required for binary file uploads such as PDFs, images, or scanned documents. Ensure the classificationId is valid, and that any provided batchId already exists within the classification context.
POST /api/v1/documentClassification/uploadFiles - Destructive
Classification: Delete classification
This endpoint permanently deletes an entire document classification process, including all associated batches, results, and uploaded files. You must provide only the classificationId in the request body. This action is irreversible and removes all data linked to the specified classification. Use this endpoint when you intend to fully decommission a classification and all its related content. Separate endpoints are available for deleting individual batches or files.
DELETE /api/v1/documentClassification/deleteClassification - Destructive
Classification: Delete batch
This endpoint permanently deletes a specific batch from a document classification process. You must provide both the classificationId and the batchId in the request body. This action is irreversible and will remove the selected batch along with all results and files associated with it. Use this endpoint when you need to clean up or remove a specific batch without affecting the overall classification. Separate endpoints are available for deleting entire classifications or individual files.
DELETE /api/v1/documentClassification/deleteBatch - Destructive
Classification: Delete files
This endpoint permanently deletes one or more specific files from a batch within a document classification process. You must provide the classificationId, batchId, and a list of fileIds in the request body. This action is irreversible and will remove the specified files and their associated results, without affecting the rest of the batch or classification. Use this endpoint to precisely remove files without deleting the entire batch or classification. Separate endpoints exist for deleting entire classifications or batches.
DELETE /api/v1/documentClassification/deleteFiles
No operations match.
See How connections work for access and permissions, or browse all integrations.