CONQUER GUIDES

Build on a shared foundation.

Use the REST API with scoped keys or OAuth access tokens. OpenAPI describes the action schemas.

Create a scoped key

Open Integrations → API access in your workspace. Choose the smallest set of permissions your integration needs. Copy the key once and store it securely. Keys expire after 90 days and can be revoked.

List projects

Send bearer credentials in the Authorization header. Never include credentials in URLs.

curl https://conquer.sh/api/v1/projects \
  -H "Authorization: Bearer $CONQUER_API_KEY"

Execute an action

POST /api/v1/actions accepts an action name and its validated arguments. Limits and workspace membership are enforced on the server.

{"action":"research_keyword","project_id":"PROJECT_UUID","keyword":"sustainable travel","country":"US"}

Handle failures honestly

400 means invalid input, 401 requires sign-in, 403 means insufficient permissions, 409 indicates a conflicting or stale operation, 429 is a rate limit, and 503 indicates missing provider configuration. Never automatically retry an uncertain publishing request.

Signed webhooks

Verify X-Conquer-Signature as HMAC-SHA256 over timestamp + "." + raw request body. Reject timestamps older than five minutes, compare in constant time, and deduplicate X-Conquer-Event-Id. Deliveries retry up to five times with exponential backoff.

X-Conquer-Signature: t=UNIX_SECONDS,v1=HEX_HMAC
X-Conquer-Event-Id: EVENT_UUID

Download the OpenAPI specification →