Frequently Asked Questions (FAQ)

Find answers to the most common questions about the Lawwwing Audit API.

How long does an audit take?

Execution time depends on the selected pipeline and the complexity of the target. Most audits complete within less than a minute.

For asynchronous requests (sync=false), create a job and periodically query the job endpoint until its status becomes completed or failed.

Which pipelines are available?

The available pipelines depend on your account and subscription.

Note

To obtain the list of available pipelines, including their identifiers and functionality, please contact the Lawwwing support team.

Do I need to include https:// in the target?

No. If the submitted target does not include a protocol, the API automatically prepends https:// before processing the audit.

What do the job statuses mean?

Audit jobs progress through the following lifecycle:

• pending — The job has been created and is waiting to be processed.
• started — The audit is currently running.
• processed — The audit completed successfully and the result field contains the output.
• error — The audit could not be completed due to an error during processing.

Once a job reaches either processed or error, its status is considered terminal and will not change.

Is the Audit API suitable for production use?

Yes. The API is designed for integration into automated workflows and applications. We recommend storing the returned job ID, polling the job endpoint until completion, and handling both successful and failed terminal states.

Where can I get support?

If you need assistance with authentication, available pipelines, limits, or enterprise integrations, please contact the Lawwwing support team at hello@lawwwing.com.