Botify API

Name: Botify API API
Brand: Botify API
Availability: InStock

✓ Official Vendor SpecMarketingSeo SemapiKey26 EndpointsREST

For Agents

Pull enterprise SEO crawl analyses, sitemap reports, internal-link metrics, and URL-level datamodel queries from Botify across 26 endpoints.

Quickstart

Get started with Botify API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"pull Botify crawl statistics"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Botify API API.

List analyses for a Botify project and inspect a specific analysis

Retrieve crawl statistics including time-series and URL lists by status type

Query URL-level data with aggregations and suggested filters

Pull sitemap audit reports and out-of-config or sitemap-only URL samples

Surface lost-PageRank URLs and link percentile distributions

GET STARTED

Start building with Botify API API

Explore with Jentic

View OpenAPI Document

Botify is an enterprise SEO platform that crawls large websites, joins crawl data with Google Analytics and log files, and surfaces technical SEO issues at scale. The API exposes analyses, projects, crawl statistics, URL-level datamodel queries, sitemap reports, internal linking metrics, and orphan URL detection so SEO teams can pipe insight into their dashboards and automation. Authentication uses a Django Rest token in the Authorization header. Use it when an enterprise site needs deep crawl analytics that go beyond a desktop crawler.

Use Cases

Patterns agents use Botify API API for, with concrete tasks.

★ Crawl status reporting into a BI dashboard

Enterprise SEO teams pull crawl health metrics from Botify into a BI dashboard so leadership can monitor indexable pages, response code distribution, and crawl duration over time. GET /analyses/{username}/{project_slug}/{analysis_slug}/crawl_statistics returns the high-level snapshot and the matching /time endpoint returns the time-series view. Most teams wire this into Looker or Power BI in a sprint.

Pull GET crawl_statistics for project mybrand-www analysis 2026-06-01 and report counts of 200, 301, 404, and 5xx URLs

Filtered URL exports for content audits

Content and SEO teams export a filtered slice of URLs (for example, low-traffic pages with thin content or pages with many internal links and no organic clicks) to drive an audit. POST /analyses/{username}/{project_slug}/{analysis_slug}/urls/export submits an export job with filters; GET /urls/export/{url_export_id} polls for completion. Audits typically run weekly with a saved filter.

Submit a URL export for analysis 2026-06-01 filtering to depth>=3 and pageviews<10, then poll the export id until complete and return the download URL

Sitemap and orphan URL hygiene

SEO teams reconcile sitemaps against the live crawl to find URLs that should be indexed but are missing from sitemaps, and orphan URLs that get organic traffic but are not internally linked. The features/sitemaps and features/ganalytics/orphan_urls endpoints surface both lists for action by the content team. This is typically run after every monthly recrawl.

Get the sitemap report and out_of_config sample for project mybrand-www analysis 2026-06-01 and return the count of out-of-sitemap URLs

Agent-driven SEO insight retrieval via Jentic

An AI agent answers questions like 'how many 404s did the latest crawl find on mybrand-www?' by calling Botify directly. Through Jentic the agent searches for 'Botify crawl statistics', loads the schema, and executes the call while the Authorization token stays inside the Jentic vault.

Search Jentic for 'Botify crawl statistics', load the schema, and execute it for project mybrand-www analysis 2026-06-01, returning the 404 count

Key Endpoints

26 endpoints — botify is an enterprise seo platform that crawls large websites, joins crawl data with google analytics and log files, and surfaces technical seo issues at scale.

METHOD

PATH

DESCRIPTION

GET

/analyses/{username}/{project_slug}

List analyses for a project

GET

/analyses/{username}/{project_slug}/{analysis_slug}/crawl_statistics

High-level crawl statistics for an analysis

POST

/analyses/{username}/{project_slug}/{analysis_slug}/urls

Query URL-level data with filters

POST

/analyses/{username}/{project_slug}/{analysis_slug}/urls/aggs

Run aggregations over URL data

POST

/analyses/{username}/{project_slug}/{analysis_slug}/urls/export

Start a filtered URL export

GET

/analyses/{username}/{project_slug}/{analysis_slug}/features/sitemaps/report

Sitemap audit report

GET

/analyses/{username}/{project_slug}/{analysis_slug}/features/pagerank/lost

Lost PageRank between analyses

GET

/projects/{username}/{project_slug}/filters

List saved filters on a project

GET

/analyses/{username}/{project_slug}

List analyses for a project

GET

/analyses/{username}/{project_slug}/{analysis_slug}/crawl_statistics

High-level crawl statistics for an analysis

POST

/analyses/{username}/{project_slug}/{analysis_slug}/urls

Query URL-level data with filters

POST

/analyses/{username}/{project_slug}/{analysis_slug}/urls/aggs

Run aggregations over URL data

POST

/analyses/{username}/{project_slug}/{analysis_slug}/urls/export

Start a filtered URL export

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Botify Django Rest token is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution access only; the raw token never enters prompts, logs, or tool outputs.

Intent-based discovery

Agents search Jentic for intents like 'pull Botify crawl statistics' or 'export Botify URLs' and Jentic returns the matching operations with their input schemas, so the agent calls the right endpoint without crawling Botify's docs.

Time to first call

Direct Botify integration: 3-5 days to handle auth, filter shapes, and async export polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Ahrefs API

Backlink and keyword data that pairs with Botify's on-site crawl analytics.

Use Ahrefs for off-site backlink and keyword data; pair Botify when the team also needs deep on-site crawl and log-file analytics.

Complementary

Semrush API

Keyword research and competitor data complementing on-site crawl analytics from Botify.

Use Semrush for keyword and competitor visibility; pair Botify for crawl-level technical SEO insight on owned sites.

Alternative

Moz API

SEO data provider with link metrics and keyword data, lighter on enterprise crawl analytics.

Use Moz for general SEO link and keyword metrics; use Botify when the priority is large-scale technical crawl analysis.

FAQs

Specific to using Botify API API through Jentic.

What authentication does the Botify API use?

Botify uses a Django Rest token in the Authorization request header (named DjangoRestToken in the spec). Generate the token from your Botify account; in Jentic it lives in the vault and is injected at execution so it never appears in agent prompts or logs.

Can I export a filtered list of URLs from a Botify analysis?

Yes. POST /analyses/{username}/{project_slug}/{analysis_slug}/urls/export with the filters in the request body to start an export job, then poll GET /analyses/{username}/{project_slug}/{analysis_slug}/urls/export/{url_export_id} for the download link. Use POST /urls/suggested_filters to discover useful filter shapes for the dataset.

How do I get crawl status counts for an analysis?

Call GET /analyses/{username}/{project_slug}/{analysis_slug}/crawl_statistics for the snapshot, or /crawl_statistics/time for a time series. To list URLs in a particular status bucket, call /crawl_statistics/urls/{list_type} with values such as ok, redirect, or error.

How do I run a URL aggregation through Jentic?

Run pip install jentic, then search Jentic for 'Botify URL aggregation', load the POST /analyses/{username}/{project_slug}/{analysis_slug}/urls/aggs schema, and execute it with the aggregation body. Jentic handles the Authorization header automatically.

What are the rate limits for the Botify API?

Botify does not document explicit per-second rate limits in the spec, but URL aggregation and export operations are heavyweight; large analyses commonly take many seconds to return. Use the export endpoint plus polling instead of repeated synchronous queries for large datasets.

Can I detect orphan URLs that get organic traffic?

Yes. GET /analyses/{username}/{project_slug}/{analysis_slug}/features/ganalytics/orphan_urls/{medium}/{source} returns URLs that received organic traffic from the specified medium and source but were not internally linked in the crawl, which is the standard input for an internal linking remediation backlog.