Skip to main content

Overview

Updates the credentials for a specific server in your stack. This endpoint allows you to add new credentials or update existing ones. All credentials are encrypted and securely stored.
Credentials are sensitive data. Ensure you’re using secure connections and keep your API keys safe.

Endpoint

Authentication

This endpoint requires an API key. Include it in the Authorization header:

Path Parameters

string
required
The unique identifier of the stack containing the server
string
required
The unique identifier of the server to update credentials for

Request Body

object
required
Object containing credential field IDs as keys and their values as values

Response

string
Confirmation message indicating credentials were updated successfully

Example Request

Configure Gmail Credentials

Configure Linear Credentials

Update Specific Credentials

Example Response

Security Features

Encryption

  • All credentials are encrypted using industry-standard encryption before storage
  • Credentials are never stored in plain text
  • Encryption keys are managed separately from the stored credentials

Access Control

  • Credentials are isolated per user and stack
  • Only the stack owner can view or modify credentials
  • API key authentication ensures secure access

Audit Trail

  • All credential updates are logged for security monitoring
  • Changes can be tracked for compliance requirements

Credential Management Best Practices

Secure Handling

Regular Rotation

  • Rotate credentials periodically for security
  • Update credentials immediately if they may have been compromised
  • Use this endpoint to update credentials when they expire

Validation

After updating credentials, verify they work:

Error Responses

Invalid credential data or format
Invalid or missing API key
Stack, server, or server not found in stack
Rate limit exceeded
Server error occurred

Next Steps

After updating credentials:
  1. Verify status: Use Get Credentials Status to confirm all required credentials are added
  2. Test functionality: Use Invoke Tool to verify tools work with the new credentials
  3. Monitor usage: Check that your applications can successfully use the tools with the updated credentials