POST /v1/core/url-encode
URL encoder
Encode a whole URL or just one component — the difference that decides whether slashes survive.
Percent-encode or decode a URL now No key, no code — 1 credit either way.
curl -X POST "$DOATHING_API/v1/core/url-encode" \
-H "x-api-key: $DOATHING_KEY" \
-H "content-type: application/json" \
-d '{"text": "a/b c", "options": {"mode": "encode"}}'
Encode a whole URL or just one component — the difference that decides whether slashes survive.
Percent-encode or decode text in component or full-URL mode.
Input
Send either a text string or a file object. A file is decoded as UTF-8 and must be one of text/plain, text/markdown, text/html, text/csv.
Response
The result carries your remaining balance alongside it, so you can track spend without a second call.
{
"text": "a%2Fb%20c",
"mode": "encode",
"scope": "component",
"request_id": "37f01edb-0163-42a1-ac51-0acaef979800",
"credits_remaining": 96
}
Cost
1 credit per call, whether it is run from the site or from the API — the credential differs, the price does not. A new account starts with 20 credits.
A rejected request still costs a credit: the authorizer decrements before the tool validates. A call rejected for a missing or invalid key is free.
Parameters
Generated from the endpoint’s own validation, so this is exactly what it accepts. A body field goes at the top level; an option goes inside options.
| Name | In | Type | Default | Notes |
|---|---|---|---|---|
| mode | options | string | "encode" | encode or decode. one of encode, decode |
| scope | options | string | "component" | component escapes everything; url keeps the structure. one of component, url |
| plus_is_space | options | boolean | false | Decode `+` as a space, as HTML forms do. |