After years in the API market, we've observed that certain types of APIs have significant potential for monetization. APIs such as Checker, Lookup, and Verification are frequently used and highly valued. Additionally, APIs that provide real-time information or extensive historical data are also in high demand.

Interestingly, we've found that some APIs, which may not initially seem to have high monetization potential, can still attract a substantial number of subscriptions. Given the vast and diverse developer community, there is always a possibility that an API will find its niche and become widely used.

Zyla API Hub supports an extensive list of APIs in over 30 distinct categories. We strive to provide the best and most comprehensive APIs in every field. If you believe your API deserves a place in our Hub, do not hesitate to upload it so we can review it and guide you through the process.

You can price your API based on the number of API calls you will offer in each plan. The prices of the plans are predefined; you just need to assign a quantity of API calls to each plan. We suggest that you define as many plans as possible to cover a wide range of needs. Remember that in Zyla API Hub, the plans are presented on a monthly basis, but customers can also pay for a year in advance by choosing annual billing.

Zyla API Hub will also review the pricing structure you have chosen and provide you with tips to improve your sales and profits.

The terms "soft limit" and "hard limit" in an API typically refer to the usage limits imposed on API keys or accounts.

- Soft limit:: This is a threshold set below the hard limit. When the soft limit is reached, users might receive warnings or notifications indicating that they are approaching their usage limit. They may still be able to make requests beyond the soft limit, but it serves as a signal to start reducing usage or upgrading the account.

- Hard limit:: This is the absolute maximum usage allowed for an API key or account. Once the hard limit is reached, the API may deny further requests, returning an error or message indicating that the limit has been exceeded. Users will need to upgrade their account or take other actions to increase their usage limits.

At Zyla API Hub, we currently only allow APIs with a Hard Limit.

The ideal uptime is 100%. We understand that this is not always achievable, so Zyla API Hub will require a minimum uptime of 99.8% for your APIs. Please note that your earnings may be affected if you do not meet this requirement, as it can result in partial or total refund requests from subscribers. If uptime repeatedly falls below 99.9%, the Zyla Labs team may temporarily or permanently suspend your API.

Yes, you can modify an API that you have previously uploaded, and each change will be reviewed by our quality control team. Keep in mind that modifying the functionality of an endpoint or the entire API can leave several customers without service or with operational problems. Therefore, it is strongly recommended not to modify the input parameters or the API response structure without prior notice to Zyla's support team. If you need to make a structural change, it is best to contact us to help you implement it with the least possible impact on subscribers. Our support team has the ability, for example, to deprecate old endpoints or notify all subscribers about a structural change.

Uploading your API to ZylaLabs is completely free. There are no initial costs, and you can upload as many APIs as you want without incurring any expenses. Zyla API Hub operates under a revenue-sharing model, ensuring a fair and beneficial partnership with API owners. Under this model, when users subscribe to your API, you, as the owner, receive 80% of the revenue generated by those subscriptions. Zyla API Hub retains the remaining 20% to cover operational costs and platform maintenance.

This revenue-sharing model encourages owners to publish their APIs on Zyla API Hub, as it provides the opportunity to reach a wider audience and generate income based on successful subscriptions. This approach fosters collaboration and incentivizes providers to offer valuable and high-quality APIs, benefiting both API owners and users within the ecosystem.

By offering a cost-free structure with revenue sharing, ZylaLabs aims to create a thriving market for APIs, supporting providers in promoting their services and offering valuable tools to developers and companies worldwide.

Regarding our monetization model, we operate on a revenue-sharing scheme, where 80% of the revenue goes to the API provider and 20% to ZylaLabs. However, this percentage may vary depending on the service level you provide (see table for more details).

The amount payable for each subscription is calculated using the following formula:

Amount to Pay = [(Amount Received − Input Processing Fee − Refunds) × Revenue Sharing %] × (100% - Output Processing Fee)

Below, we detail this formula:

- Amount Received:: This is the total amount we receive from customers according to the subscription plan they chose.

- Input Processing Fee:: This is the fee Stripe charges for processing the payment, generally around 3%. However, it may increase if there are disputes.

- Refunds:: These are refunds issued to customers according to our return policy.

- % Revenue Share:: This is your revenue participation percentage, calculated according to the table above.

- Output Processing Fee (2%):: A fixed fee charged by the payout gateway when funds are disbursed. It is deducted within the Amount to Pay as shown in the formula.

Keep in mind that payments will be made 60 days after the API Consumer’s payment is received to accommodate potential claims or disputes that may result in a refund. Payments to API Providers are referred to as “Payouts” and can be requested from the “Payments Received” section. Once the received payments meet the conditions described above, the API Provider can request the Payout, which will be processed within 5 business days. Payouts are processed via PayPal to the account defined by the API Provider in Account Settings.

•At least 60 days must have passed since the customer's payment was received.

•There should be no disputes with the customer, or if there are, they must have been won.

•The Uptime in the month the payment was received must be at least 95%.

•The amount charged must not have been refunded.

The service level is determined by calculating the ratio of successful calls versus errors over the last 30 days. This method provides a clear and reliable view of API performance.

The Soft Limit is an additional preset usage threshold that is enabled by default. This functionality allows limited extra usage beyond the contracted plan and can be managed from the settings.

Yes, users have the option to disable the Soft Limit in their account settings in Zyla API Hub at any time.

Soft Limit invoices are generated at the end of each billing cycle and will be available at the beginning of the new cycle.

If the Soft Limit invoice is not paid, Zyla API Hub reserves the right to suspend the account. No refunds will be issued for the subscription period affected by the suspension.