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 Custom Fields API

The Custom Fields API from AWeber — 5 operations for creating, reading, renaming and deleting the custom subscriber fields defined on a list.

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

Tagged areas include Custom Fields. 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 5 operations across 2 paths, and defines 2 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.

5 operations 2 paths 2 schemas 1 DELETE2 GET1 PATCH1 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 Custom Fields 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 5

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

Custom Fields 5

What is it? Represents the custom fields associated with a list. Use this set of resources to retrieve, create, modify, and delete the custom fields that are defined for subscribe…

GET
/accounts/{accountId}/lists/{listId}/custom_fields
Get custom fields
getCustomFields 4 params → 200401403404410500503
POST
/accounts/{accountId}/lists/{listId}/custom_fields
Add custom field
addCustomField 2 params body → 201400401403404405410500
GET
/accounts/{accountId}/lists/{listId}/custom_fields/{customFieldId}
Get custom field
getCustomField 3 params → 200400401403404410500503
DELETE
/accounts/{accountId}/lists/{listId}/custom_fields/{customFieldId}
Delete custom field
deleteCustomField 3 params → 200400401403410500503
PATCH
/accounts/{accountId}/lists/{listId}/custom_fields/{customFieldId}
Update custom field
updateCustomField 3 params body → 209400401403404410500503

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are CustomField (6 properties), CustomFields (6 properties). Each schema is shown below with its type and property counts.

CustomFields
object
6 properties
CustomField
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aweber-custom-fields-api-openapi.yml Raw ↑

Other APIs AWeber publishes across the network.

AWeber Accounts API
AWeber Broadcasts API
AWeber Campaigns API
AWeber Landing Pages API
AWeber Lists API
AWeber Segments API
AWeber Subscribers 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 Custom Fields 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.