githubEdit

post__register

POST /register

Register Bridge Node

Register a new bridge node with the Flashback platform using cryptographic signature verification for authentication.

This endpoint allows bridge nodes to register themselves with the platform without requiring traditional authentication. Instead, it uses RSA signature verification to ensure the request comes from an authorized organization key.

Key Features:

  • Cryptographic signature verification using RSA keys

  • Automatic node-key association upon successful registration

  • Support for multiple cloud providers (AWS, GCS, Azure, S3-compatible)

  • Node status and region tracking

  • 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

Supported Providers:

  • S3: AWS S3 and S3-compatible services

  • GCS: Google Cloud Storage

  • AZURE: Azure Blob Storage

Validation:

  • All required fields must be present

  • Provider type must be valid

  • Signature must be cryptographically valid

  • Timestamp must be recent to prevent replay attacks

TypeScript Client Library

Code Samples

Body parameter

Parameters

Name
In
Type
Required
Description

body

body

object

true

Node registration data

» provider

body

string

true

Cloud storage provider type

» ip

body

string

true

Node IP address (used as unique identifier)

» status

body

string

true

Node status (e.g., active, inactive)

» region

body

string

true

Geographic region of the node

» version

body

string

true

Node software version

» 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)

Enumerated Values

Parameter
Value

» provider

S3

» provider

GCS

» provider

AZURE

Example responses

200 Response

400 Response

Responses

Status
Meaning
Description
Schema

200

Node registered successfully

Inline

400

Validation error or invalid signature

Inline

500

Registration 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 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.

Last updated

Was this helpful?