Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/wbiztool-com:wbiztool-com-account-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: WbizTool Account API
version: 1.0.0
summary: Send WhatsApp messages from your own number over a REST API.
description: 'The WbizTool REST API sends WhatsApp messages (text, images and files, to numbers and groups, now or scheduled) from your own WhatsApp number, linked to WbizTool the way WhatsApp Web is linked to a phone. It is not the official WhatsApp Business API. Most endpoints authenticate with `client_id` and `api_key` sent in the request body (JSON or form fields), never in a header; the number verification endpoints use an `Authorization: Bearer` header instead. Always read the JSON body and check its `status` field, because some errors come back with HTTP 200. Guides, examples in cURL, Python, Node.js and PHP, and every error message: https://wbiztool.com/docs/'
termsOfService: https://wbiztool.com/terms/
contact:
name: WbizTool support
email: info@wbiztool.com
url: https://wbiztool.com/contact-us/
servers:
- url: https://wbiztool.com/api/v1
description: Production
tags:
- name: Account
description: Credential and health checks.
paths:
/me/:
post:
operationId: checkCredentials
tags:
- Account
summary: Check credentials
description: Confirm that `client_id` and `api_key` work together and, optionally, that a WhatsApp number ID belongs to the workspace. Sends nothing and does not count as a message.
externalDocs:
description: Full documentation
url: https://wbiztool.com/docs/check-my-creds-api/
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CheckCredentialsRequest'
examples:
withNumber:
value:
client_id: 12345
api_key: YOUR_API_KEY
whatsapp_client: 678
summary: Key and number
keyOnly:
value:
client_id: 12345
api_key: YOUR_API_KEY
summary: Key only
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/CheckCredentialsRequest'
responses:
'200':
description: Valid credentials.
content:
application/json:
schema:
$ref: '#/components/schemas/CredentialsOk'
examples:
ok:
value:
status: 1
message: Okay
name: aman@example.com - 919876543210
'400':
description: 'Refused: `Auth Error - Please send correct API key and Client id`, `Invalid client id.`, `Auth Error: invalid api key`, `This API key is not linked to a workspace. Create a new API key in WbizTool.`, `Invalid WhatsApp Client ID`.'
content:
application/json:
schema:
$ref: '#/components/schemas/ApiError'
examples:
badKey:
value:
status: 0
message: 'Auth Error: invalid api key'
summary: 'Auth Error: invalid api key'
badNumber:
value:
status: 0
message: Invalid WhatsApp Client ID
summary: Invalid WhatsApp Client ID
'405':
description: Not a POST request.
content:
application/json:
schema:
$ref: '#/components/schemas/ApiError'
examples:
method:
value:
status: 0
message: Method not allowed, use POST
summary: Method not allowed, use POST
'500':
description: Unexpected server error.
content:
application/json:
schema:
$ref: '#/components/schemas/ApiError'
examples:
internal:
value:
status: 0
message: Internal error, please try again
summary: Internal error, please try again
security: []
/status/:
get:
operationId: getApiStatus
tags:
- Account
summary: API health check
description: 'Liveness check: needs no credentials, accepts any method and always returns the same body. It does not check credentials or whether a number is connected. The JSON body is served with `Content-Type: text/html`; parse it as JSON whatever the header says.'
externalDocs:
description: Full documentation
url: https://wbiztool.com/docs/check-my-creds-api/#checking-the-api-is-up
security: []
responses:
'200':
description: The API is reachable.
content:
application/json:
schema:
type: object
properties:
status:
type: integer
enum:
- 200
data:
type: object
examples:
up:
value:
status: 200
data: {}
components:
schemas:
CredentialsOk:
type: object
required:
- status
- message
- name
properties:
status:
type: integer
enum:
- 1
message:
type: string
enum:
- Okay
name:
type: string
description: Username of the workspace's creator, plus ` - <phone>` when `whatsapp_client` was sent.
ApiError:
type: object
description: A failed request. `status` is `0` and `message` says why. (`Account Disabled` has no `status` field.)
required:
- message
properties:
status:
type: integer
enum:
- 0
message:
type: string
Credentials:
type: object
description: Your API credentials, sent in the request body (JSON or form fields) of every request that uses them. Both come from Settings → API keys in the dashboard. The API key decides which workspace the request acts on.
required:
- client_id
- api_key
properties:
client_id:
type: integer
description: Your API Client ID from Settings → API keys.
examples:
- 12345
api_key:
type: string
description: One of your API keys from the same page. Keep it secret.
examples:
- YOUR_API_KEY
WhatsappClientId:
type: integer
description: ID of the WhatsApp number (or Telegram account) to send from, shown as "ID …" on the number's card on WhatsApp numbers in the dashboard.
examples:
- 678
CheckCredentialsRequest:
allOf:
- $ref: '#/components/schemas/Credentials'
- type: object
properties:
whatsapp_client:
$ref: '#/components/schemas/WhatsappClientId'
description: 'Optional: also check that this number ID belongs to the key''s workspace (deleted numbers fail).'
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: 'Number verification endpoints only: `Authorization: Bearer YOUR_API_KEY` (a key from Settings → API keys). Other endpoints take `client_id` and `api_key` in the body (see the `Credentials` schema).'
apiKeyQuery:
type: apiKey
in: query
name: api_key
description: Alternative for the GET number verification endpoints; the header keeps the key out of logs.
externalDocs:
description: WbizTool API documentation
url: https://wbiztool.com/docs/