What you need
- The API access add-on for your organization. Read Add-ons. For prices, go to perquery.ai/en/pricing.
- An API key. Read API keys.
Base URL
All requests go to this base URL:/v1. For example, the list of your sites is at https://perquery.ai/api/v1/sites.
Main rules
- Read-only. The API accepts only
GETrequests. A request with another method gets403. - JSON. The API sends JSON responses. Error responses use
application/problem+json. Read Errors and limits. - API key in each request. Send your key in the
Authorizationheader. Read Authentication. - Same access as the key creator. A key reads only the data that the roles of its creator allow at the time of the request.
- UUIDs. Sites, prompts and other resources have a UUID. Paths use it, for example
/v1/sites/{site_uuid}/prompts.
What you can read
An API key can read these types of data:- Your sites, prompts, personas and competitors.
- The results of visibility scans and the answers of the AI engines.
- The results of content analysis, technical analysis, authority and bot logs.
- Opportunities and impact tracking.
- The status of your integrations.
Your first request
1
Create an API key
Create a key on the API Keys page of the app. Copy the key when the app shows it. Read API keys.
2
Send a request
Replace
pq_xxxxxxxxxxxx_your_secret with your key and run this command:3
Read the response
The API answers
200 with a JSON object. The sites list holds the sites of your organization. Use the uuid of a site in the paths of the other endpoints.Cached responses
Some endpoints send anETag header. Send this value back in the If-None-Match header of the next request. When the data did not change, the API answers 304 with no body.

