Read surfaces
- Sites and connection health
- Runs and activity summaries
- Rankings, evidence and findings
- Experiments, proposals and usage
Explore SEOForge
REST API
Build on scoped SEO operations—not hidden production authority.
The public contract is designed for inspection and bounded workflow requests. Endpoint examples below illustrate the intended versioned shape and must be checked against the current OpenAPI document before implementation.
Nothing publishes without approvalPaid product accessNo ranking guarantees
curl https://api.seoforge.example/v1/sites/site_123/runs \ -H "Authorization: Bearer $SEOFORGE_TOKEN"
Illustrative hostname and command.
Resource model
Sites own evidence; runs produce findings and proposals.
Permanently unavailable
- Approve or reject as another human
- Merge a repository change
- Deploy or publish production content
- Retrieve credentials or bypass protection
Authentication
Bearer identity plus workspace, site and environment scope.
Create and revoke service tokens inside the authenticated product. Store them in a secret manager, never in source or client-side code.
Scopes
Explicit read and request permissions.
sites:read runs:read findings:read proposals:read runs:request webhooks:manage
Rate limits
Read response headers; limits follow endpoint and paid capacity.
On 429, honor Retry-After and use exponential backoff with jitter. Use supported idempotency keys on request endpoints and cache stable reads.
Errors
Machine-readable code, safe message and request ID.
HTTP/1.1 403
{ "error": { "code": "scope_denied", "request_id": "req_example" } }Paid deployment · human authority
API access is part of an authorized paid workspace.
Talk to sales if your integration needs service identities, higher limits or multiple environments.