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

AWeber Authentication API

The Authentication API from AWeber — 4 operations covering the OAuth 2.0 token and revoke endpoints on auth.aweber.com plus the legacy OAuth 1.0a request-token and access-token endpoints that remain published and live. OAuth 2.0 authorization code, with PKCE required for public clients, is the only supported model for new applications.

AWeber Authentication API is one of 12 APIs that AWeber publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and a getting-started guide.

This API exposes 4 operations across 4 paths, organized into 2 resource areas. It is described by OpenAPI 3.0.2, at version 1.0.

Requests are made against a single base URL, https://api.aweber.com/1.0.

4 operations 4 paths 0 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.2
API Version
1.0
Base URL
https://api.aweber.com/1.0
Authentication
OAuth 2.0
Resource Areas
2

Authentication & Security 1

AWeber Authentication API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth 2.0) using the authorizationCode flow, exposing 9 scopes. By default, every request must be authenticated.

  • OAuth 2.0 — The following endpoints and scopes are used to authenticate.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 POST. They span 2 resource areas: OAuth 1.0a Reference, OAuth 2.0 Reference. Each is listed below with its method, path, parameters, and response codes.

OAuth 1.0a Reference 2
POST
/oauth/request_token
Get a request token
getARequestToken body → 200400401410500503
POST
/oauth/access_token
Get an access token
getAnAccessToken body → 200400401410500503
OAuth 2.0 Reference 2

These endpoints are used to authenticate with the api. The AWeber API uses the OAuth 2.0 model to handle authentication. OAuth is a standardized way for services to grant permissi…

POST
/oauth2/token
Get a token
getAToken 1 param body → 200400401410500503
POST
/oauth2/revoke
Revoke a token
revokeAToken 1 param body → 200400401410500

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aweber-authentication-api-openapi.yml Raw ↑

Other APIs AWeber publishes across the network.

AWeber Accounts API
AWeber Broadcasts API
AWeber Campaigns API
AWeber Custom Fields API
AWeber Landing Pages API
AWeber Lists API
AWeber Segments API
AWeber Subscribers API
AWeber Web Forms API
AWeber Integrations API
AWeber Beta API
Where this information came from

This is an independent, third-party profile of AWeber Authentication 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.