post__unregister

POST /unregister

Unregister Bridge Node

Remove a bridge node from the Flashback platform using cryptographic signature verification for authentication.

This endpoint allows bridge nodes to unregister themselves from the platform without requiring traditional authentication. It uses RSA signature verification to ensure the request comes from an authorized organization key.

Key Features:

• Cryptographic signature verification using RSA keys

• Removes node from the platform registry

• Cleans up node-key associations

• Minimal required fields for unregistration

• Version information capture for compatibility monitoring

Authentication:

• No traditional authentication required

• Uses RSA signature verification for security

• Signature must be generated using a valid organization private key

• Timestamp validation prevents replay attacks

Validation:

• IP address is required for node identification

• Signature must be cryptographically valid

• Timestamp must be recent to prevent replay attacks

• Node must exist in the registry

TypeScript Client Library

public nodeUnregister = async (data: RegisterRequest): Promise<RegisterResponse> => {
  return this.makeRequest<RegisterResponse>('unregister', 'POST', data);
};

Code Samples

Shell

# You can also use wget
curl -X POST https://backend.flashback.tech/unregister \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '{
    "ip": "192.168.1.100",
    "timestamp": "2024-01-15T10:30:00.000Z",
    "signature": "base64-encoded-signature",
    "id_org": "org-123e4567-e89b-12d3-a456-426614174000"
  }'

HTTP

JavaScript

Ruby

Python

PHP

Java

Go

Body parameter

{
  "ip": "192.168.1.100",
  "timestamp": "2024-01-15T10:30:00.000Z",
  "signature": "base64-encoded-signature",
  "id_org": "org-123e4567-e89b-12d3-a456-426614174000"
}

Parameters

Name	In	Type	Required	Description
body	body	object	true	Node unregistration data
» ip	body	string	true	Node IP address (used as unique identifier)
» timestamp	body	string	true	Request timestamp for signature verification
» signature	body	string	true	RSA signature of the request data
» id_org	body	string	false	Organization ID (optional)

Example responses

200 Response

{
  "success": true,
  "message": "Unregistration successful"
}

400 Response

{
  "success": false,
  "message": "Missing required fields"
}

404 Response

{
  "success": false,
  "message": "Node not found"
}

Responses

Status	Meaning	Description	Schema
200	OK	Node unregistered successfully	Inline
400	Bad Request	Validation error or invalid signature	Inline
404	Not Found	Node not found in registry	Inline
500	Internal Server Error	Unregistration failed	Inline

Response Schema

Status Code 200

Name	Type	Required	Restrictions	Description
» success	boolean	false	none	Operation success status
» message	string	false	none	Success message

Status Code 400

Name	Type	Required	Restrictions	Description
» success	boolean	false	none	Operation success status
» message	string	false	none	Error message describing the validation issue

Status Code 404

Name	Type	Required	Restrictions	Description
» success	boolean	false	none	Operation success status
» message	string	false	none	Error message indicating node not found

Status Code 500

Name	Type	Required	Restrictions	Description
» success	boolean	false	none	Operation success status
» message	string	false	none	Error message describing the internal error

This operation does not require authentication as it uses cryptographic signature verification for security.