Introduce your API to the depot.
Help us understand what your API does, who it serves, and where developers can find reliable documentation. A useful listing begins with a clear capability and an official reference.
What to include
Email the provider name, public website, official API documentation link, and a concise explanation of the capability. Identify the intended use case, supported integration approach, and the category that best fits. If the API requires special onboarding or has relevant access conditions, point to the public documentation that explains them.
Explain the developer experience
A practical description helps someone understand the input their application must provide and the result they can expect. Describe authentication, the main request types, and the guidance available for errors and operational limits. Keep claims concrete and supply sources for details that need verification.
How suggestions are reviewed
We consider relevance to the depot, clarity of the documented capability, and the usefulness of the available integration guidance. Sending a suggestion does not guarantee a listing or a publication date. The goal is a coherent resource that helps readers assess a service on its actual merits.
Include public documentation and a short use-case summary.
Keep an existing guide accurate
If your service is already listed, send the profile URL and the official source that supports a requested correction. Changes are assessed against our editorial standards. Provider names and factual descriptions do not imply sponsorship, partnership, or an endorsement of every use case.