Couchdrop Developer Docs
Couchdrop HomepageKnowledge BaseLogin
  • Couchdrop API Overview
  • Available Endpoints
  • Errors and Response Codes
  • Domains and Accounts
    • Register a new domain
    • Manage domain/account
    • Authentication
  • Administration
    • Users
    • Groups
    • Folder Permissions
    • Folder Properties
    • Shared Links
    • Storage Connections
      • SFTP Connections
      • S3 Connections
      • FTP Connections
      • Azure Connections
      • GCS Connections
      • Other
    • Automations
      • Scheduled Automations
        • Create/Update
        • Get all schedule workflows
        • Get schedule workflow
        • Trigger schedule workflow
        • Delete Scheduled Workflow
      • Event Automations
        • Create/Update
        • Get action workflow
        • Get all action workflows
        • Delete Action Workflow
      • Actions
        • Webhook
        • Rename
        • Copy
        • Move
        • PGP Encrypt
        • Paths
      • Conditions
    • Symlinks/Shortcuts
    • Auditing and Reporting
  • Webhooks
    • Using webhooks
  • Filesystem Operations
    • Listing files/folders
    • Downloading a file
    • Uploading a File
    • Rename files/folders
    • Deleting files/folders
    • Create a folder
Powered by GitBook

Couchdrop

  • Couchdrop Homepage
  • Register
  • Login

Platform

  • Cloud SFTP Server
  • Cloud FTP Server
  • Automated Transfers
  • Mailboxes and Inboxes

Copyright Couchdrop Limited 2025

On this page

Was this helpful?

Errors and Response Codes

All API methods return a HTTP status code which indicates success or failure.

It isĀ important that you handle different API response codes properly.

Status Code
Description

200

A status code of 200 indicates success. There should normally be a body returned with this status code that includes the data or result set.

403

HTTP 403 means you do not have the correct permissions to perform that operation. It is a fatal error and should not be retried.

429

HTTP 429 means you have exceeded our rate limiting protection mechanisms. In this case, we recommend implementing a exponential backof mechanism and retrying the request in a short period of time.

422

HTTP 422 is a response returned on error by the fileio service. In this case, there is an upstream error from the cloud storage provider and the error details can be found in the response.

503

HTTP 503 normally indicates a capacity issue on our end. Treat this the same as a 429 and implement an exponential back-of mechanism.

500

HTTP 500 indicates and unexpected error. Check the body for more details and implement a short retry/exponential backoff mechanism.

PreviousAvailable EndpointsNextRegister a new domain

Last updated 2 years ago

Was this helpful?