# Update AT Communication Details Updates the AT communication details stored for the given context and type. username and password are always required here, and are checked against the AT before they are stored. Endpoint: PUT /api/v3/account_credentials Version: 3.1.0 Security: apiKeyAuth ## Query parameters: - `api_key` (string, required) Your API Key. Example: "YOUR_API_KEY" ## Request fields (application/json): - `account_credential` (object, required) context and type are always required. username and password are required on PUT, and on POST unless use_legacy_credentials is true. The username must start with the account's NIF (format NIF/subuser). - `account_credential.username` (string) Example: "123456789/1" - `account_credential.password` (string) Stored encrypted (AES-256-CBC, Base64-encoded), so the usable plaintext length is meaningfully shorter than the underlying column width. No exact limit is published. Example: "test123" - `account_credential.context` (string, required) Enum: "Invoices", "Guides", "Sequences" - `account_credential.type` (string, required) Enum: "AT" - `account_credential.use_legacy_credentials` (boolean) POST only. When true, the credentials are copied from the account's existing (legacy) AT communication details instead of username/password, which may then be omitted. Fails with 422 when the account has no legacy credentials or already has credentials. ## Response 200 fields (application/json): - `success` (boolean) Example: true - `http_code` (string) Enum: "created", "ok" ## Response 404 fields (application/json): - `errors` (array) Example: [{"error":"Missing required params."}] - `errors.error` (string) ## Response 500 fields (application/json): - `errors` (array) Example: [{"error":"An unexpected error occurred"}] - `errors.error` (string)