AWeber uses OAuth 1.0a to secure our API. This standard is a way for developers to prove they have permission to access customer accounts without ever knowing an AWeber customer’s password. This is accomplished is with a set of keys that tell which integration is requesting data and show that the customer allowed the integration to access their account.
I am a developer, setting up a new integration:
If you are a developer creating a new integration for AWeber, whether for your own use or for general use by customers, you will need to set up an OAuth 1.0a flow for your integration. It sounds daunting, but we have a great getting started guide that can help. The guide also contains a example code to make things as easy as possible for you.
If you have any trouble, don’t hesitate to reach out to us at email@example.com and we’ll be happy to help!
I am an AWeber customer, trying to use an integration:
The API keys (consumer key, consumer secret, access token, and access secret) are only needed by developers following the OAuth 1.0a authentication protocol. AWeber customers should never need to create a developer account unless they are a developer creating an integration themselves.
If an integration has asked you to provide API keys or consumer keys, they have not implemented authentication for AWeber accounts correctly. Please contact their support team and ask them to reach out to us at firstname.lastname@example.org. We can help guide them through this set up.
In the meantime, you might want to use a different, properly secured integration. Our integrations showcase highlights hundreds of excellent integrations that can help you with your email marketing tasks.