Pugpig Security API
Pugpig tries to make it as easy as possible for you to either sell or provide access to protected content. In many cases, you will want to take advantage of the payment ecosystems provided by the large App Store vendors who have seamless one-click payments from In App Purchases, and a large number of credit cards already on file. This is provided entirely out of the box. In other cases, you will want to allow your existing users access to content. These might live in a third party subscription system, or simply in a database you manage. It is also very common to allow access for multiple sources in the same application. As all systems are different, we can only provide out of the box integrations for the larger, well known subscription systems. However, we do provide a tried and tested pattern for integrating with any system. This section of the knowledge base attempts to answer all questions you may have while doing this, from the technical, UX and even some commercial perspectives. However, if this does not answer your question please get in touch with us and we will see what we can do.
- Integrating PKCE authentication & receipt postback for Piano
- Issue-based vs Access-based Subscriptions
- Web-based authentication integrations in Pugpig apps using PKCE
- Security API - What is needed to integrate with the Pugpig security API
- Security API - Security Flow Chart and Documentation Overview
- Server Side Security - Interfaces
- Security API - Specification
- Security API - HTTP Security Headers
- Security API - App Store In App Purchases
- Security API - Pugpig Security API Explanation
- Using your own security or subscription system
- Existing App Third Party Subscription System Integrations
- General Security Considerations
- API Glossary