Create or update a secret

POST 
/api/v1/secrets/put

Writes or replaces a value under name; this upsert also rotates the stored credential. The response contains metadata only, and no public read endpoint returns the value. Name-based bindings remain the same, but consumers can retain prior values in caches or in-flight work; this is not upstream credential revocation.

Value storage and metadata updates are separate steps. On an error, metadata alone cannot confirm which value is current. Stop using the affected binding and contact your Travila operator before retrying.

The following access conditions are preserved as declared intent and are not implemented by generated code: Authorized tenant project secret administration.

Use this in a guide: Connect a private tool without putting its credential in prompts · Answer questions about a website using your own Firecrawl account · Secret values and credential references

Request

Responses

200

Secret written; metadata only

Store an example-named provider credential; replace the placeholder with the value to store.

Section ID: DOC-CP-secrets-api-putSecret#example-secrets-putSecret-request

Request example

{
  "name": "travel-provider-api-key",
  "value": "replace-with-provider-api-key",
  "description": "API key for the travel provider"
}

Guide request for 1. Store the Firecrawl credential. Replace example resource identifiers with your own authorized values.

Section ID: DOC-CP-secrets-api-putSecret#example-cookbook-integrations-tools-connections-custom-mcp-servers-01-request

Request example

{
  "name": "firecrawl-api-key",
  "value": "fc-your-token-here",
  "description": "Firecrawl bearer token",
  "labels": {
    "kind": "mcp-auth"
  }
}

Guide request for Rotate the credential. Replace example resource identifiers with your own authorized values.

Section ID: DOC-CP-secrets-api-putSecret#example-cookbook-integrations-tools-connections-custom-mcp-servers-06-request

Request example

{
  "name": "firecrawl-api-key",
  "value": "fc-the-new-token"
}

Illustrative response shape; omitted default fields and actual outcomes depend on the operation.

Section ID: DOC-CP-secrets-api-putSecret#example-secrets-putSecret-response

Response example

{
  "metadata": {
    "name": "example",
    "projectId": "example_123",
    "description": "example",
    "labels": {},
    "version": "1",
    "createdBy": "example",
    "createdAt": "2026-09-16T12:00:00Z",
    "updatedAt": "2026-09-16T12:00:00Z"
  }
}

Document ID: DOC-CP-secrets-api-putSecret. Section identities and revisions.

Section	Stable reference
Create or update a secret	DOC-CP-secrets-api-putSecret#overview
Request	DOC-CP-secrets-api-putSecret#request
Responses	DOC-CP-secrets-api-putSecret#responses