Find answers about authentication, API credits, security, rate limits, and getting started with WyldAPI.
WyldAPI is a growing library of developer-friendly micro-APIs - Email Checker, ZIP/Postal Lookup, DNS Checks, and Bin Packing - that you can plug in quickly to handle common backend tasks. It's token-based and managed from a web console.
Generate an API key in the WyldAPI console and include it in your request headers as documented in-app.
WyldAPI is token-based and the console lets you create and manage up to 3 keys.
WyldAPI provides real-time request logs and usage stats in the console. For details on what's logged and retention, refer to the in-app documentation or policy page.
WyldAPI runs on a simple credit system instead of a monthly plan. Some endpoints are free to use, while premium APIs draw from a shared pool of credits - each call to a premium endpoint spends credits from your balance. You start with free credits, so you can test an API against your real use case before paying anything. When you need more, you top up your balance; larger top-ups unlock higher limits and added flexibility. There are no subscriptions to manage - you pay for what you use and scale as your needs grow.
API keys are created and managed from the WyldAPI console. Once you're logged in, open the API Keys section and create a new key, then copy it somewhere safe - you'll use it to authenticate your requests. Each account can hold up to three API keys, so you can keep separate keys for different projects or environments.
Yes. You manage all your keys from the API Keys section of the console. If a key is ever exposed, or you just want to rotate it, remove the old key and create a replacement - because each account supports up to three keys, you have room to swap one out. Update your application with the new key, and the old one stops working.
WyldAPI grows based on what developers need, so requests are welcome. If you hit a bug or want a new endpoint added, send a support request with the details - which API, what you expected, and what happened. And if you find yourself rebuilding the same backend task across projects, tell us; new APIs get added based on developer requests.
Every account's API keys and data are fully isolated - your keys, request logs, and usage stay private to your account and separated from everyone else's. To keep your key safe on your end, store it server side rather than in client side code, keep it out of public repositories and shared links, and rotate it (remove and recreate) if you suspect it's been exposed.
No - once you receive your free credits, or pay for credits, those are yours forever until they’re used.
Premium endpoints use credits, and some endpoints are free to try. Limits and quotas are tied to your plan/credits - see the pricing page and in-app docs for specifics.
Yes. You can test with free credits before paying in the API playground.
Core coverage includes US and CA. If you need a specific country, contact us and we can look at adding additional support.
WyldAPI is a growing library of developer-friendly micro-APIs - Email Checker, ZIP/Postal Lookup, DNS Checks, and Bin Packing - that you can plug in quickly to handle common backend tasks. It's token-based and managed from a web console.
Generate an API key in the WyldAPI console and include it in your request headers as documented in-app.
WyldAPI is token-based and the console lets you create and manage up to 3 keys.
WyldAPI provides real-time request logs and usage stats in the console. For details on what's logged and retention, refer to the in-app documentation or policy page.
WyldAPI runs on a simple credit system instead of a monthly plan. Some endpoints are free to use, while premium APIs draw from a shared pool of credits - each call to a premium endpoint spends credits from your balance. You start with free credits, so you can test an API against your real use case before paying anything. When you need more, you top up your balance; larger top-ups unlock higher limits and added flexibility. There are no subscriptions to manage - you pay for what you use and scale as your needs grow.
API keys are created and managed from the WyldAPI console. Once you're logged in, open the API Keys section and create a new key, then copy it somewhere safe - you'll use it to authenticate your requests. Each account can hold up to three API keys, so you can keep separate keys for different projects or environments.
Yes. You manage all your keys from the API Keys section of the console. If a key is ever exposed, or you just want to rotate it, remove the old key and create a replacement - because each account supports up to three keys, you have room to swap one out. Update your application with the new key, and the old one stops working.
WyldAPI grows based on what developers need, so requests are welcome. If you hit a bug or want a new endpoint added, send a support request with the details - which API, what you expected, and what happened. And if you find yourself rebuilding the same backend task across projects, tell us; new APIs get added based on developer requests.
Every account's API keys and data are fully isolated - your keys, request logs, and usage stay private to your account and separated from everyone else's. To keep your key safe on your end, store it server side rather than in client side code, keep it out of public repositories and shared links, and rotate it (remove and recreate) if you suspect it's been exposed.
No - once you receive your free credits, or pay for credits, those are yours forever until they’re used.
Premium endpoints use credits, and some endpoints are free to try. Limits and quotas are tied to your plan/credits - see the pricing page and in-app docs for specifics.
Yes. You can test with free credits before paying in the API playground.
Core coverage includes US and CA. If you need a specific country, contact us and we can look at adding additional support.