API Proxy

⚡ Built-in — Platform Built-in

Route external API calls through our server to bypass CORS restrictions. Register target URLs and call them from your published pages without worrying about cross-origin issues.

⚡ Built-in — No Setup Required This integration is built into the WebsitePublisher platform. All endpoints are available immediately — no API key needed.

Try it with your AI assistant

Once WebsitePublisher is connected to your AI assistant, paste one of these into the chat. Replace the parts in [brackets] with your own details.

ChatGPT Claude Other assistants

@WebsitePublisher show live data from [API URL] on my page through the API proxy, with my API key kept in the vault

@WebsitePublisher register [API name] at [URL] so my page can call it without CORS errors

With WebsitePublisher, show live data from [API URL] on my page through the API proxy, with my API key kept in the vault

With WebsitePublisher, register [API name] at [URL] so my page can call it without CORS errors

With WebsitePublisher, show live data from [API URL] on my page through the API proxy, with my API key kept in the vault

With WebsitePublisher, register [API name] at [URL] so my page can call it without CORS errors

Endpoints (4)

POST register

Register a new external API endpoint for proxying. Requires a paid plan (Starter, Pro, or Agency). For an API that needs a key: send api_key, or set vault_key to the name of a secret the owner stored in the dashboard Vault. Auth can go in a header (bearer, api_key_header, custom_header) or in the query string (query_param). list shows per endpoint whether its key is present. Optional (#366): {name} placeholders in target_url with validation rules in path_params (e.g. map tiles), a shared GET cache (cache_ttl_secs) and a hard monthly cap on calls to the target (monthly_upstream_cap).

Field	Type	Required
`name`	string	✓ Yes
`target_url`	url	✓ Yes
`path_params`	object	No
`cache_ttl_secs`	integer	No
`monthly_upstream_cap`	integer	No
`methods`	array	No
`auth_type`	string	No
`auth_header_name`	string	No
`api_key`	string	No
`vault_key`	string	No
`forward_headers`	object	No
`rate_limit`	integer	No

POST update

Update an existing proxy endpoint configuration

Field	Type	Required
`name`	string	✓ Yes
`target_url`	url	No
`path_params`	object	No
`cache_ttl_secs`	integer	No
`monthly_upstream_cap`	integer	No
`methods`	array	No
`auth_type`	string	No
`auth_header_name`	string	No
`api_key`	string	No
`vault_key`	string	No
`forward_headers`	object	No
`rate_limit`	integer	No
`is_active`	boolean	No

POST remove

Remove a proxy endpoint and its vault secrets

Field	Type	Required	Description
`name`	string	✓ Yes

GET list

List all configured proxy endpoints for this project

No input parameters required.

MCP Tool Names

When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:

Endpoint	MCP Tool Name
register	`api-proxy_register`
update	`api-proxy_update`
remove	`api-proxy_remove`
list	`api-proxy_list`

← Back to all integrations