MAZ offers a set of APIs which can be used by you to create your own Database Integrations.

Navigate to Users, and select Database Integrations from the dropdown.

Select Custom Integration. 

1. Enter an Integration Name

The custom name of the integration.

2. Select Subscription Type

The subscription type has two implications. First, it defines the unlocking mechanism in your apps. And second, it will determine the formatting of your API response. The subscription types are: 

3. Manage Login Types

This setting defines how your users will authenticate their subscription (ie. by entering email and password OR entering email and zip code, etc.). This is the user-generated data set that will be sent from MAZ to your API. 

4. Provide Test Credentials

Provide test credentials to test various scenarios like Active/Expired/Invalid users in your app. You should provide at least one set of test credentials for each if the three cases viz. Active subscriber, Expired subscriber and Invalid subscriber. And this should be done for each login type.

5. Enable / Disable Single Sign-On (SSO)

Single Sign-On = OFF: One-way sync API endpoint

Single Sign-On = ON: Two-way sync API endpoint

6. Subscription Status URL

Enter the API URL where MAZ should send user login information and determine subscription access.

7. Notes

You may add some notes for either MAZ or for internal communication regarding your Custom Integration.

The straight forward one-way database integration to validate and unlock app access for your existing subscribers hosted in your database. 

The Subscription Status API will check the current status of the user’s subscription. Subscription statuses can be requested when an existing user is signing-in and MAZ has no record of the user or when syncing access for print subscribers. 

A successful response will return a status of "active": “true” for All-Access authentication and start and end dates of the subscription for Duration Based access as : "startDate" and "endDate".
​

An SSO database integration solution to validate and unlock app access for your existing subscribers hosted in your database and data sync of in-app subscriber and single in-app purchases(feeds) records back to your database.
​

The User Registration API will be used to pass user login info from MAZ apps and create a new record in your database. If a new user is created, you will return a “success” response and the UID (member_id) of the new user. The member_id should be the ID for this user within your database. Based on which registration/authentication cases configured for your outputs, the parameters included in the response will vary.

We expect a member_id in response if the sign-up went through; member_id is the ID of the resource in the external database. This ID will be later used to make subscription purchase API calls whenever a digital subscription is purchased in the app.

2. Subscription Status

The Subscription Status API will check the current status of user’s subscription. Subscription Statuses can be requested when an existing user is signing-in and MAZ has no record of the user or when syncing access for print subscribers. 

A successful response will return a status of "active": “true” for All-Access authentication and a start and end date of the subscription for Duration Based access as : "startDate" and "endDate".

Note : With Subscription Status API request we expect you to accept "subscriber_data" hash.

The Subscription Update API will create a new subscription record in your database when a user purchases a subscription within a MAZ app. MAZ will periodically send subscription update calls to maintain consistent subscription records across all databases.

4. Reset Password

The Reset Password API will be used to trigger your internal reset password mechanism. A successful response will indicate that the email id has been found in your database and an email has been / will be sent to the user’s email id.

Please note that you will need to whitelist the following IP addresses of MAZ servers at your end for Database Integration to work:

65.39.196.50
65.39.196.56
65.39.196.73
65.39.196.251
65.39.138.111

65.39.196.230
65.39.196.235
65.39.196.233

65.39.196.234
69.90.55.132
69.90.55.134
69.90.55.133

To simplify the testing process, we have provided a testing environment on the Custom Integration page. 

Using the “+Parameter” icon, add the parameters that you wish to test and fill in some testing data. When you click “Try Now” MAZ will ping your API URL, displaying both the request and the response. As noted above, you’ll need to match the response associated with your subscription type to successfully authenticate a subscriber. 

Note: Parameters must be enabled under “Login Type” before being added for testing.

You’ll want to test your integration in an app environment to be certain everything is working smoothly. The Custom Integration controls are connected directly to your app, so any changes made in the dashboard will go live immediately. That means you’ll be able to live test as soon as you update the dashboard. 

Please reach out to the MAZ Success team at success@mazsystems.com for any queries.