Skip to main content
PATCH
Update Token Documentation

Overview

The PATCH /patch-token-docs endpoint allows you to update token-related documentation and branding materials for existing tokens. This endpoint handles file uploads for token logos, subscription agreements, and legal documents.

Key Features

  • Token Logo Upload: Upload token logotype images to S3 storage
  • Legal Document Management: Upload subscription agreements and legal documents to IPFS
  • Multipart Form Data: Supports file uploads through multipart/form-data format
  • Selective Updates: All file fields are optional - update only what you need
  • Off-chain Update: This endpoint does not prepare or require any blockchain transaction

Request Format

This endpoint accepts multipart/form-data with the following fields:

Required Fields

  • tokenSymbol (string): The symbol of the token being updated

Optional File Fields

  • tokenLogotype (image file): Logo image for the token (uploaded to S3)
  • subscriptionAgreement (PDF file): Subscription agreement document (uploaded to IPFS)
  • legalDocs (PDF file): Legal documentation (uploaded to IPFS)

Example Request

Response Format

Success Response (200)

Response Fields

File Storage Details

Token Logotype

  • Storage: Amazon S3
  • Supported Formats: Image files (PNG, JPG, etc.)
  • Access: Direct S3 URL reference
  • Use Case: Token branding and display
  • Storage: IPFS (InterPlanetary File System)
  • Supported Formats: PDF files
  • Access: IPFS CID (Content Identifier)
  • Use Case: Immutable legal document storage

Security & Authorization

  • API Key Required: Include your API key in the x-api-key header
  • Token Ownership: You can only update documentation for tokens associated with your account
  • File Validation: Files are validated for type and size before upload
  • No Transaction Signature: API key requests do not require signerAddress, txId, or signed transactions

Error Handling

Common Error Responses

400 Bad Request
401 Unauthorized

Use Cases

  1. Brand Updates: Update token logos for better visual representation
  2. Legal Compliance: Upload updated subscription agreements and legal documents
  3. Documentation Management: Maintain current legal and compliance documentation
  4. Token Maintenance: Keep token information up-to-date post-creation

Important Notes

  • Only the tokenSymbol field is required - all file uploads are optional
  • Files are processed and uploaded to different storage systems based on their purpose
  • IPFS storage ensures immutable document storage for legal compliance
  • S3 storage provides fast access for branding materials
  • This endpoint is fully off-chain: token logos are uploaded to S3, documents are uploaded to IPFS, and the token database record is updated without preparing a blockchain transaction
  • The endpoint validates file types and user permissions before processing uploads

Authorizations

x-api-key
string
header
required

Body

multipart/form-data
tokenSymbol
string
required

The symbol of the token being updated.

tokenLogotype
object

Image file for the token's logo.

subscriptionAgreement
object

PDF file for the token's subscription agreement.

PDF file containing the legal documentation.

Response

Successful update

success
boolean

Indicates if the operation was successful.

Example:

true

tokenSymbol
string

The token symbol that was updated.

tokenLogotypeRef
string

Reference (e.g., S3 path) to the uploaded token logotype image.

subscriptionAgreementIpfs
string

IPFS CID reference to the uploaded subscription agreement.

IPFS CID reference to the uploaded legal documents.