Audit API
Lawwwing Audit analyses a website's compliance status and produces a structured report. It is designed to qualify prospects and support the sale: you identify the gaps on a website that is not yet a customer and use that diagnosis in the commercial conversation.
If you are already a partner, you can run audits manually from the dashboard. The API lets you automate the same flow from your CRM, your website or your own lead-capture tools.
The Audit API is part of Lawwwing Integrations. Authenticated calls need a token that we issue after the onboarding process.
What does it bring to your sales process?
| Benefit | Description |
|---|---|
| Data-backed prospecting | You analyse a lead's website before the meeting and arrive with a concrete diagnosis. |
| Sales argument | The report turns non-compliance into a visible need for the prospect. |
| Two ways to use it | You run it by hand from the partner dashboard or automate it through the API. |
| Fits your systems | The API slots into a CRM, a capture form or the onboarding of a potential customer. |
Partner dashboard or API
| Partner dashboard | API | |
|---|---|---|
| Usage | Manual, case by case | Programmatic, from your systems |
| Ideal for | One-off meetings and demos | Volume, CRMs and capture flows |
| Access | Available in the partner dashboard | API token after onboarding |
The result is the same analysis. The API exists so you can launch it and retrieve it without going through the dashboard, when Audit is part of an automated process.
How does the API work?
| Step | In your sales flow | Call to Lawwwing | Result |
|---|---|---|---|
| 1 | You identify a prospect and their website | POST /api/v1/jobs/ | You get the job id |
| 2 | You wait for the analysis to finish | GET /api/v1/jobs/{job_id}/ | The job moves through pending and started |
| 3 | You use the report in the sale | Not applicable | When the status is processed, result contains the diagnosis |
The analysis is asynchronous by default: you create the job, store the identifier and poll the status until it finishes. Most audits complete in less than a minute.
Prerequisites
Before integrating the API, make sure that:
- You have your own backend able to make authenticated calls. The token must never be exposed in the browser.
- You have the API token we issue after the onboarding process.
- You have a place to display or store the report, for example the lead record in your CRM.
Technical reference
The canonical reference for endpoints, parameters and responses is the Audit API documentation:
This documentation explains the use case, access and the integration flow. For the detail of each field, use the reference above.
How do I get started?
- Request access and receive your API token.
- Follow the integration guide to create a job and retrieve the result.
- Check the API reference when you need the details of an endpoint.