quaxar-asm-seed-add-batch

Syntax

quaxar-asm-seed-add-batch profile=STRING

Options

profile=STRING: Required. QUAXAR connect profile code. This is a write operation, so exactly one profile must be specified.

Input fields

Field	Type	Required	Description
seed_type	string	Y	Seed type to register. IP, DOMAIN, CIDR. Can be replaced by the type field
type	string	N	Fallback field used when seed_type is absent
value	string	Y	Seed value to register. e.g. example.com, 192.0.2.0/24

Output fields

Field	Type	Name	Description
result	string	Result	OK when registered
_error	string	Error	Failure reason when registration fails (absent on success)

Error codes

Parsing errors

Error message	Cause	Resolution
Specify valid Quaxar profile.	Missing profile option	Specify a profile code in profile
Batch command requires exactly one profile.	More than one profile specified	Specify exactly one profile
No available Quaxar profile found.	No Quaxar connect profile registered	Register a Quaxar connect profile first

Runtime errors

Per-row failures do not stop the pipeline; they are flowed to the _error field of the affected row.

Error message	Cause	Resolution
seed_type(type) or value field not found	Input row has no seed_type/type or value	Fill in both fields in the input
quaxar asm api error: status=..., message=...	ASM API returned an error to the register request	Check seed value format and profile permission

Description

Caution

This is a write command. It registers a new seed in Quaxar ASM for each input row, and registered seeds become scan targets. Before running, verify that the input pipeline contains only the intended seeds.

quaxar-asm-seed-add-batch is a batch command that reads the seed_type (or type if absent) and value fields of each incoming row and registers them as new seeds. The seed type value is normalized to uppercase before it is sent. If either field is missing, that row is not registered; instead the reason is placed in the _error field and the row is passed through. A single row failure does not stop the whole pipeline, so after execution you can filter failed rows by the _error field.

Because it is a write operation, exactly one profile must be specified.

Examples

Example: Bulk-register seeds from a CSV list

Situation: You want to read a list of new managed domains and IP ranges from a file and register them all at once as Quaxar ASM seeds.

csvfile seeds.csv
| quaxar-asm-seed-add-batch profile=my_profile

Expected result:

seed_type	value	result
DOMAIN	example.com	OK
CIDR	192.0.2.0/24	OK

Interpretation: A row with result OK was registered successfully. Filter only rows where the _error field is populated to inspect the failure cause and retry.