How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

BrightEdge Pages API

The Pages API from BrightEdge — 2 operation(s) for pages.

BrightEdge Pages API is one of 30 APIs that BrightEdge publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Pages. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 3 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 5.0.0.

Requests are made against the base URL https://api.brightedge.com.

3 operations 2 paths 5 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5.0.0
Base URL
https://api.brightedge.com
Authentication
HTTP Basic, API Key, API Key, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 6

BrightEdge Pages API declares 6 security schemes for authenticating requests. It accepts HTTP basic authentication (http_basic). An API key is passed in the header as X-Forwarded-Authorization (forwarded_http_basic). An API key is passed in the cookie as BRIGHTEDGE (session_cookie). An API key is passed in the header as X-BRIGHTEDGE-SESSION (session_header). An API key is passed in the header as X-Token (api_token_header). An API key is passed in the header as Bearer-Token (bearer_token).

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Pages 3
GET
/5.0/pages/keywords/primary_secondary
Get Primary/Secondary Keywords
keywords_5_0_pages_keywords_primary_secondary_get 2 params → 200422
GET
/5.0/pages/details
Get Page Details
pages_5_0_pages_details_get 2 params → 200422
POST
/5.0/pages/details
Update Page Details
pages_5_0_pages_details_post body → 200422

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are PageDetails (5 properties), PageDetailsInput (4 properties), ValidationError (3 properties), PSKeywords (2 properties). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
PSKeywords
object
2 properties
PageDetailsInput
object
4 properties 2 required
PageDetails
object
5 properties 4 required
ValidationError
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

brightedge-pages-api-openapi.yml Raw ↑

Other APIs BrightEdge publishes across the network.

BrightEdge accounts API
BrightEdge ai_catalyst API
BrightEdge autopilot API
BrightEdge backlinks API
BrightEdge be_local API
BrightEdge budd API
BrightEdge bulk_export API
BrightEdge chrome_extension API
BrightEdge chromeextension API
BrightEdge core API
BrightEdge dataset API
BrightEdge domains API
Where this information came from

This is an independent, third-party profile of BrightEdge Pages API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.