✔️ OAuth 2.0 ✔️ Segments ✔️ App promotion!

Published: Thu, 05/30/19

New! Support for Segments

Earlier this month, we added Get Segments and Get Segment endpoints to our API. We also updated our Create Broadcast and Update Broadcast endpoints to accept a segment.

The benefit: These combined changes allow you to send a Broadcast to a segment (or group) of customers in your integration.

Go to the API documentation!

OAuth 2.0 FAQs

Here are some of the most common questions we’ve received from developers that have implemented OAuth 2.0:

How do I migrate from OAuth 1.0a to OAuth 2.0?
Create a new OAuth 2.0 app and update your integration to support OAuth 2.0 along with OAuth 1.0a. This gives you the flexibility to migrate at the speed and convenience that works best for you and your customers.
Why should I use PKCE?
Keep your app secure. If others can see your client secret, then they can send calls on your behalf. PKCE eliminates this problem.
When and how do I refresh my token?
OAuth 2.0 requires you to refresh your token. We documented token expiration and various ways to perform a token refresh.
How do permissions work in OAuth 2.0?
In OAuth 2.0, permissions are called scopes. We documented which scopes are required to access our various endpoints.

If you have a question, please contact us at [email protected].

Drive More Interest in Your App

Want to get the word out about your app? Get featured on our Integrations Showcase! (It’s free.) If approved, your app will get:

inclusion on the AWeber website
a dedicated landing page to promote to your audience
an article written by our customer success team that explains how to connect your app to AWeber’s platform (promoted via AWeber in our Knowledge Base for all customers)

Showcase my integration

Happy coding and have a great day!

Jake W.
Business Development Manager - Integrations

Zac G.
Product Manager - Integrations