Connect a custom endpoint - The Prompting Company

Use the custom endpoint integration when your CMS is not natively supported. The Prompting Company POSTs JSON to your endpoint with a bearer token.

Endpoint requirements

Your server must:

The response body is logged in TPC but not parsed.

TPC sends the token you paste into the integration form as:

Authorization: Bearer <token>

Validate this on your endpoint before processing the request. Reject anything without a valid bearer with 401.

Use placeholders to map TPC’s fields into your endpoint’s expected shape. Available placeholders:

Example body template:

{
  "title": "{{title}}",
  "html": "{{content}}",
  "cover": "{{heroImageUrl}}"
}

TPC substitutes placeholders before sending. Unset placeholders resolve to empty string.

If your endpoint needs extra headers (API key, tenant ID), paste them as a JSON object in the integration form:

{ "X-Tenant-Id": "abc123" }

Open Settings → Integrations in your TPC product workspace.
Select Custom endpoint.
Enter:
- Endpoint URL — the fully qualified URL TPC should POST to
- Bearer token — the token your server will validate
- Body template — JSON with placeholders
- Custom headers — optional JSON object
Click Save, then Test connection.

TPC waits up to 30 seconds. Confirm the endpoint is publicly reachable and responds within that window.

Your endpoint rejected the bearer token. Confirm the token stored in your server matches the one pasted into TPC.

Return a 2xx status only after the write is durable. Any non-2xx response is treated as a failure and shown as an error in the publish log.