Akta: Action Doc

Checking the status of an asynchronous Akta request.

Tool ID: akta_request_status

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'akta_request_status',
  {
    "request_id": "request_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute akta_request_status --input '{
  "request_id": "request_123"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "status": "example",
    "data": {
      "request_id": "request_123",
      "request_type": "example",
      "status": "example"
    }
  }
}

Use deepline tools get akta_request_status --json for the latest machine-readable contract.

Input reference

Returns the current status of an asynchronous request, such as a company addition request, by its request ID. This is a free endpoint — it does not consume API credits.

Name	Type	Required	Default	Details
`payload.request_id`	`string`	Yes	—	The unique identifier of the request to check, returned when the original request was submitted. Example: 2db01b38-5c81-4b3f-b76d-8b36aeed603b

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.status`	`string`	No	—	—
`result.data.data`	`object`	No	—	—
`result.data.data.request_id`	`string`	No	—	Unique identifier of the request being tracked.
`result.data.data.request_type`	`string`	No	—	The type of request. Example: company_addition
`result.data.data.status`	`string`	No	—	Current status of the request. Possible values: pending, in_progress, completed, failed.
`result.data.data.created_at`	`string`	No	—	Timestamp when the request was created, in ISO 8601 format.
`result.data.data.updated_at`	`string`	No	—	Timestamp when the request was last updated, in ISO 8601 format.
`result.data.data.detail`	`object`	No	—	Request-type-specific details for company_addition request.
`result.data.data.detail.company_addition_request_id`	`string`	No	—	Identifier of the underlying request record.
`result.data.data.detail.company_name`	`string`	No	—	Name of the company submitted for addition.
`result.data.data.detail.domain`	`string`	No	—	Resolved domain of the submitted company.
`result.data.data.detail.status`	`string`	No	—	Status of the underlying request. Possible values: pending, in_progress, completed, failed.
`result.data.data.detail.reason`	`string \| null`	No	—	Explanation when the request did not succeed. null unless the request has failed.
`result.data.data.detail.company_uuid`	`string \| null`	No	—	Akta UUID of the company once it has been added. null until the request is completed.
`result.data.data.detail.created_at`	`string`	No	—	Timestamp when the underlying request was created, in ISO 8601 format.
`result.data.data.detail.updated_at`	`string`	No	—	Timestamp when the underlying request was last updated, in ISO 8601 format.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation