Information Sources
Keep, replace or remove stored secrets in a source configuration
A source configuration can hold secrets: API tokens, passwords, and secret headers or cookies that Rapidflare sends when it fetches your content. Rapidflare stores them, uses them, and never shows them again. This page explains what you see in their place and how to keep, replace or remove them.
What you see in place of a stored secret
Every stored secret comes back as the placeholder __rf_redacted__. You see it in the dashboard, in API responses and in MCP tool results. No one can read a stored secret back through the dashboard, the API or MCP, including Rapidflare staff.
{
"ingestion_config": {
"type": "confluence",
"base_url": "https://example.atlassian.net/wiki",
"api_token": "__rf_redacted__"
}
}
These values are hidden:
- connector credentials, such as API tokens, passwords, client secrets and security tokens;
- cookies;
- custom fetch headers. Every header is hidden except a few that never carry a credential:
User-Agent,Referer,Accept,Accept-Language,Accept-Encoding,Cache-Control,PragmaandDNT; - any text value in a field Rapidflare does not recognize.
URLs are shown exactly as stored. A credential written inside a URL, such as https://user:password@host or a token in the query string, is not hidden. Put credentials in a header or a credential field instead.
In the dashboard, a stored secret shows as a Saved secret chip in place of its value, under a note that stored secrets are hidden.
Keep, replace or remove a secret
You choose what happens to each stored secret by what you do with its placeholder:
| To | Do this |
|---|---|
| Keep the secret | Leave __rf_redacted__ unchanged. Rapidflare puts the stored value back when you save. |
| Replace the secret | Put the new value where the placeholder was. |
| Remove the secret | Remove the key. With an API PATCH, send null instead (see Replace and merge). |
The placeholder only keeps a secret when it is sent back exactly as __rf_redacted__, at the same place. If there is no stored secret at that place, the save is refused.
Edit secrets in the dashboard
To edit a source's secrets in the dashboard, open the source's Configurations tab and choose Edit. Each stored secret shows as a Saved secret chip in the editor, and a list under the editor names every stored secret with what will happen to it when you save.
- Keep it. Leave the chip alone.
- Replace it. Click the chip (or put the cursor beside it and press Enter) and type or paste the new value. What you type is hidden; use Show to check it before saving. Press Esc to put the saved secret back. Until you save, you can click the new value to edit it again, or use Use saved secret to go back to the stored one. A secret can't be saved empty.
- Remove it. Use Remove in the list under the editor. Use Restore to bring it back until you save. If the source needs that secret to connect, Save waits until you enter a new value or restore it.
- No partial edits. A secret can't be edited in part. An edit that would damage it is refused, with a message saying what to do instead.
- A check before saving. When a save replaces or removes a secret, the dashboard lists those secrets and asks you to confirm. A save that keeps every secret goes straight through.
- New domain. If a save would send a kept secret to a new domain, the dashboard marks that secret and asks you to enter it again (see below).
The Add source step for a custom JSON configuration works the same way.
Re-enter secrets after a domain change
Secrets cannot be redirected to new domains. When you point a source at a different domain, you must type its stored secrets again: Rapidflare will not send a secret somewhere new unless someone has decided to send it there.
This applies when a save:
- changes the address a connector sends requests to (its base URL, site URL, subdomain or proxy) to one on a different domain. Moving within the same domain is fine:
wiki.example.comcan becomedocs.example.comorexample.com. Moving fromhttptohttpson the same host or domain is fine too. A different port, a move fromhttpsback tohttp, or any change of proxy counts as a new address; - adds a URL on a different domain to a source with a list of URLs, such as a URL list or a sitemap. Adding a URL on a domain the list already uses is fine, and so is removing URLs;
- changes the source's connector type.
Rapidflare compares domains the way browsers do, using the Public Suffix List. Sites that each customer gets on a shared platform count as different domains: two github.io sites, two vercel.app sites, two Atlassian Cloud sites such as acme.atlassian.net and other.atlassian.net, and two wordpress.com sites. An IP address, localhost, or a name with no public domain, such as intranet, must stay exactly the same.
If such a save keeps a stored secret, it is refused. The API answers 422 with the error type secret_requires_reentry_for_new_destination and names each secret to re-enter. Enter the secrets again in the same save, and it goes through.
Copy a source with its secrets
You can copy a source without anyone seeing its secrets. A copied configuration carries the placeholders, plus copy_secrets_from set to the id of the original source. Each placeholder in the new source takes the value the original source stores at the same place.
The original source must belong to your organization and use the same connector type. The domain rule above still applies: if the copy points at a different domain, enter the secrets again.
In the dashboard, paste the copied configuration into the Add source custom JSON step. Its secrets show as Copied from chips naming the original source. If the copy points at a different domain, the create is refused and the step marks the secrets to enter again. Enter them, or use Undo domain change to put back the original source's addresses and keep the copied secrets.
For API and MCP users
The API applies the rules above to every write, and the MCP tools that update sources go through the same API.
Replace and merge
PUT /api/v1/sources/{source_id}/configurationreplaces the configuration whole. A secret you leave out is removed. Send__rf_redacted__to keep it.PATCH /api/v1/sources/{source_id}/configurationmerges your body into the stored configuration (JSON Merge Patch). A secret you leave out is kept. Send a new value to replace it, ornullto remove it.
Get the current configuration, with every secret as a placeholder, from GET /api/v1/sources/{source_id}/configuration.
Check a change first with a dry run
Send the same PUT or PATCH to its dry-run path, /api/v1/dry-run/sources/{source_id}/configuration. Rapidflare validates the change, including every secret rule on this page, and answers with a preview of what would change. Nothing is saved, and every answer from a dry-run path carries the header RF-Preview: 1. Treat an answer without that header as "no preview was made". ?dry_run=true on the configuration routes themselves also previews, but the dry-run path is safer: a server that doesn't know dry runs refuses an unknown path rather than saving the change.
Errors
A refused write returns 422, saves nothing, and lists each problem with its error type and the field path (loc) it applies to. Errors never include a secret value.
| Error type | Meaning |
|---|---|
secret_placeholder_damaged | A value is an altered copy of the placeholder. Send __rf_redacted__ exactly to keep the secret, or send a new value. |
redacted_value_without_stored_secret | The placeholder is at a place where no secret is stored, so there is nothing to keep. |
secret_requires_reentry_for_new_destination | The save keeps a stored secret while moving it to a new domain or connector type. Send the secret again. |