Aller au contenu

Incident du 12/11/2026 résolu

Lire le rapport

MCP pour agents IA30 outilsVotre agent IA travaille avec les droits que vous lui accordez. Enregistrer, transférer et résilier restent dans l’espace client. Si vous lui en donnez le droit, il peut récupérer le code de transfert d’un domaine : au maximum 3 récupérations par domaine et par jour, chacune consignée dans le journal.

Lire la documentation MCP
TLS certificates
v1.10.0
Download OpenAPI

Update TLS organization

Update the local TLS organization contact data used for readiness checks and order completion.
PATCH
/tls/organization/{organization_id}
TLSOrganizationsByID

Authentication

x-api-keyapplication/json

Parameters

Name
Type
Format
Required
Description
organization_id
path
string
-
Required
Public TLS organization ID

Request body

application/jsonRequired
Partial TLS organization payload
tlsOrganizationPatchRequest
tlsOrganizationPatchRequest
{
  "edit_mode": "create_replacement",
  "organization": "example",
  "first_name": "example",
  "last_name": "example"
}

Fields

Name
Type
Format
Required
Description
edit_mode
create_replacement, update_provider
string
-
Optional
-
organization
string
-
Optional
-
first_name
string
-
Optional
-
last_name
string
-
Optional
-
address
string
-
Optional
-
postal_code
string
-
Optional
-
city
string
-
Optional
-
country_code
string
-
Optional
-
phone
string
-
Optional
-
email
string
-
Optional
-

Request example

PATCH
curl --request PATCH \
  --url 'https://api.regfish.com/tls/organization/hdl_7K9QW3M2ZT8HJ' \
  --header 'x-api-key: YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --data '{
  "edit_mode": "create_replacement",
  "organization": "example",
  "first_name": "example",
  "last_name": "example"
}'

Responses

200
TLS organization updated
application/jsontlsOrganizationResponse
Response example 200
{
  "success": true,
  "code": 0,
  "response": {
    "id": "hdl_7K9QW3M2ZT8HJ",
    "organization": "example",
    "status": "ready",
    "usable_for_ordering": true,
    "first_name": "example",
    "last_name": "example",
    "address": "example",
    "postal_code": "example",
    "city": "example",
    "country_code": "example",
    "phone": "example",
    "email": "example"
  }
}
400
Invalid request payload
application/jsonError
Response example 400
{
  "success": false,
  "message": "Invalid request payload",
  "error": "Invalid request payload"
}
401
Unauthorized
application/jsonError
Response example 401
{
  "success": false,
  "message": "Unauthorized",
  "error": "Unauthorized"
}
404
TLS organization not found
application/jsonError
Response example 404
{
  "success": false,
  "message": "TLS organization not found",
  "error": "TLS organization not found"
}
500
Unexpected error
application/jsonError
Response example 500
{
  "success": false,
  "message": "Unexpected error",
  "error": "Unexpected error"
}
Community

Devenez membre de la communauté

L'API DNS regfish est une excellente solution pour les développeurs qui souhaitent automatiser les domaines et les zones DNS. Faites partie de la communauté et bénéficiez de l'automatisation DNS. L'API DNS est disponible gratuitement pour chaque client regfish.