OLAB Assist REST API

What you get

• Endpoints for account, sites, site detail, findings, AI answers, score history and changes.
• Sites can be addressed by id or domain, e.g. /sites/example.com.
• Paging with next_cursor, 120 requests per minute per key.
• A versioned contract: within v1 fields are only added, never removed or renamed.

Before you start

• An OLAB Assist account on the Agency plan, signed in as the account owner.
• A tool that can send HTTP requests with a header (curl, Postman, your CRM, a script).

Set it up step by step

1. 1

   Create a key

   Integrations → API keys: name it after the tool (e.g. “HubSpot sync”) and click Create key. Copy it now; it is shown only once.

2. 2

   Make your first request

   Send the key in the Authorization header. The example below lists your sites with their latest scores.

3. 3

   Pick the data you need

   Use /sites/{site} for the full picture, /findings for issues, /answers for AI answers and /history for scores over time. The full reference is in the developer docs.

4. 4

   Schedule it

   Run your import daily or after each scan.completed webhook, so you never poll more than needed.

curl https://api.olabassist.com/api/v1/sites \
  -H "Authorization: Bearer olab_YOUR_KEY"

Tips

• One key per integration: revoking it affects only that tool.
• Ignore fields you do not know. New ones are added over time and your code keeps working.
• For Google Sheets, an Apps Script with UrlFetchApp and a daily trigger is enough.

Troubleshooting

Questions