API Documentation
Introduction
API Documentation
Introduction
Welcome to the MyBetterLead API 👋
MyBetterLead provides a simple yet powerful solution to enhance lead activation.
Our API is built around REST principles, featuring:
- Predictable, resource-oriented URLs
- JSON-encoded request and response bodies
- Standard HTTP response codes, authentication methods, and verbs
- Integrate MyBetterLead into your software to streamline your workflow, transform processes, and save valuable time when searching for someone’s LinkedIn profile.
Status Codes
The MyBetterLead API adheres to standard HTTP response codes to indicate the outcome of API requests:
- 2xx: Successful operations
- 3xx: Redirections
- 4xx: Client-side errors, often due to invalid or missing input
- 5xx: Server-side errors, often due to a problem with the API service
| Code | Name | Description |
|---|---|---|
| 200 | OK | The request was successful. |
| 400 | Bad Request | The request was invalid. |
| 401 | Unauthorized | The request requires authentication. |
| 403 | Forbidden | The server understood the request but refuses to authorize it. |
| 404 | Not Found | The requested resource was not found. |
| 405 | Method Not Allowed | The request method is not supported for the requested resource. |
| 429 | Too Many Requests | The client has sent too many requests in a given amount of time. |
| 500 | Internal Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. |