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 Subscribers API

The Subscribers API from AWeber — 12 operations for adding, reading, updating, moving, searching and deleting subscribers on a list, reading subscriber activity, and recording tracked purchases.

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

Tagged areas include Subscribers. 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 12 operations across 6 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

12 operations 6 paths 10 schemas 2 DELETE5 GET2 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.aweber.com/1.0
Authentication
OAuth 2.0, OAuth 2.0
Resource Areas
1

Authentication & Security 2

AWeber Subscribers API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth_2.0) using the authorizationCode flow, exposing 9 scopes. 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.
  • OAuth 2.0 — The following endpoints and scopes are used to authenticate.

Paths & Operations 12

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

Subscribers 12

What is it? Represents a collection of subscribers. Use this set of resources to add, remove, find, and update an AWeber Customer Account's subscribers. The collection responses a…

GET
/accounts/{accountId}/lists/{listId}/subscribers
Get subscribers
getSubscribers 5 params → 200400401403404410500503
POST
/accounts/{accountId}/lists/{listId}/subscribers
Add subscriber
addSubscriber 2 params body → 201400401403404410415500
DELETE
/accounts/{accountId}/lists/{listId}/subscribers
Delete subscriber by email
deleteSubscriberByEmail 3 params → 200400401403404410500503
PATCH
/accounts/{accountId}/lists/{listId}/subscribers
Update subscriber by email
updateSubscriberByEmail 3 params body → 209400401403404410415500
GET
/accounts/{accountId}/lists/{listId}/subscribers/{subscriberId}
Get subscriber
getSubscriber 3 params → 200400401403404410500503
POST
/accounts/{accountId}/lists/{listId}/subscribers/{subscriberId}
Move subscriber
moveSubscriber 3 params body → 201400401403404405410415
DELETE
/accounts/{accountId}/lists/{listId}/subscribers/{subscriberId}
Delete subscriber by ID
deleteSubscriberByID 3 params → 200400401403404410500503
PATCH
/accounts/{accountId}/lists/{listId}/subscribers/{subscriberId}
Update subscriber by ID
updateSubscriberByID 3 params body → 209400401403404410415500
GET
/accounts/{accountId}/lists/{listId}/subscribers?ws.op=find
Find subscribers for list
findSubscribersForList 35 params → 200400401403410500503
GET
/accounts/{accountId}?ws.op=findSubscribers
Find subscribers for account
findSubscribersForAccount 32 params → 200400401403404410500503
GET
/accounts/{accountId}/lists/{listId}/subscribers/{subscriberId}?ws.op=getActivity
Get subscriber activity
getSubscriberActivity 6 params → 200400401403404410500503
POST
/accounts/{accountId}/lists/{listId}/purchases
Create a purchase
createAPurchase 2 params body → 202400401403404410415500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Subscriber (29 properties), Purchase (14 properties), AddSubscriberRequestBody (10 properties), UpdateSubscriberRequestBody (9 properties). Each schema is shown below with its type and property counts.

MoveSubscriberRequestBody
object
4 properties 2 required
Subscribers
object
7 properties
SubscriberGetActivity
object
5 properties
Activity
object
6 properties
AddSubscriberRequestBody
object
10 properties 1 required
Subscriber
object
29 properties
UpdateSubscriberRequestBody
object
9 properties
Purchase
object
14 properties 9 required
FindSubscribersAccount
object
7 properties
FindSubscribers
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aweber-subscribers-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 Integrations API
AWeber Beta Endpoints API
AWeber OAuth 1.0a Reference API
AWeber OAuth 2.0 Reference API
AWeber Webforms API
Where this information came from

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