Validate a WordPress site URL + plugin API key without storing them
Validate a WordPress site URL + plugin API key without storing them. Returns the key's scopes, the WordPress user it acts as, its rate limit and the detected permalink style. the same facts POST /v1/wordpress/connections would store. Use this to check a…
Request
- x-api-key: <your-api-key>
- Content-Type: application/json
Response
{
"endpointCount": 3,
"key": {},
"ok": true,
"pluginVersion": "1.0.0",
"restStyle": "<rest style>",
"site": "<site>",
"status": "success"
}What it does
Validate a WordPress site URL + plugin API key without storing them. Returns the key's scopes, the WordPress user it acts as, its rate limit and the detected permalink style. the same facts POST /v1/wordpress/connections would store. Use this to check a key before connecting. Free.
Request
Body
| Field | Type | Required | Description |
|---|---|---|---|
apiKey | string | yes | Plugin API key (cwl_...) to validate |
url | string | yes | Site address, e.g. https://example.com |
Example request
{
"apiKey": "<your-api-key>",
"url": "https://example.com/page"
}Response
| Field | Type | Description |
|---|---|---|
endpointCount | integer | |
key | object | |
ok | boolean | |
pluginVersion | string | |
restStyle | string | |
site | string | |
status | string |
Example response
{
"endpointCount": 3,
"key": {},
"ok": true,
"pluginVersion": "1.0.0",
"restStyle": "<rest style>",
"site": "<site>",
"status": "success"
}Errors
Every error answers with the same envelope: an HTTP status, a machine code and a sentence.
400 | The body or a parameter failed validation. The details array names the field. |
401 | No key, a revoked key or a wrong header. Send x-api-key. |
402 | The wallet cannot cover this call. Top up or wait for the monthly grant. |
404 | The resource does not exist, or it is not yours. Both answer identically and cost nothing. |
429 | Over the per-minute quota of your tier. Back off and retry. |
5xx | Upstream refused or timed out. The call is not billed. |
Code
curl -X POST 'https://app.castomapi.com/v1/wordpress/connections/test' \
-H 'x-api-key: <your-api-key>' \
-H 'Content-Type: application/json' \
-d '{"apiKey": "<your-api-key>", "url": "https://example.com/page"}'const res = await fetch('https://app.castomapi.com/v1/wordpress/connections/test', {
method: 'POST',
headers: { 'x-api-key': '<your-api-key>', 'Content-Type': 'application/json' },
body: JSON.stringify({"apiKey": "<your-api-key>", "url": "https://example.com/page"})
});
const data = await res.json();
console.log(data);import { request } from 'node:https';
// Node 18+ has fetch built in
const res = await fetch('https://app.castomapi.com/v1/wordpress/connections/test', {
method: 'POST',
headers: { 'x-api-key': '<your-api-key>', 'Content-Type': 'application/json' },
body: JSON.stringify({"apiKey": "<your-api-key>", "url": "https://example.com/page"})
});
const data = await res.json();
console.log(data);import requests
res = requests.post(
'https://app.castomapi.com/v1/wordpress/connections/test',
headers={'x-api-key': '<your-api-key>'},
json={"apiKey": "<your-api-key>", "url": "https://example.com/page"},
timeout=30,
)
print(res.json())<?php
$ch = curl_init('https://app.castomapi.com/v1/wordpress/connections/test');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => ['x-api-key: <your-api-key>', 'Content-Type: application/json'],
CURLOPT_POSTFIELDS => json_encode(['apiKey' => '<your-api-key>', 'url' => 'https://example.com/page']),
]);
$data = json_decode(curl_exec($ch), true);
print_r($data);Cost and limits
This operation costs metered. A call that fails is never billed. Every account gets 1000 free tokens a month; paid balances never expire.
Rate limits per minute
| No key | 10 |
| Free | 60 |
| Pro | 300 |
| Enterprise | 1200 |
Questions
What does Validate a WordPress site URL + plugin API key without storing them cost?
metered per successful call, debited from your wallet after the response. Failed calls are free. Every account receives 1000 free tokens a month.
How do I authenticate?
Send your key in the x-api-key header. One key covers every metered endpoint; there is nothing to enable per endpoint.
Can I send an Authorization: Bearer token instead?
Not for a metered endpoint — those take the x-api-key header and nothing else. Bearer tokens belong to the account side: the dashboard and account APIs accept a JWT session, and castomapi-auth issues those through a standard OAuth2 handshake, with authorization code, client credentials and refresh grants. The auth service page covers it.
What are the limits?
10 requests a minute per IP with no key at all, 60 a minute on the free tier, 300 on Pro, 1200 on Enterprise. Above the no-key tier the quota is per account, across every endpoint.
OpenAPI: https://app.castomapi.com/docs/json